From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 11898 invoked from network); 2 Mar 2023 07:35:14 -0000
Received: from minnie.tuhs.org (50.116.15.146)
  by inbox.vuxu.org with ESMTPUTF8; 2 Mar 2023 07:35:14 -0000
Received: from minnie.tuhs.org (localhost [IPv6:::1])
	by minnie.tuhs.org (Postfix) with ESMTP id E730443BE4;
	Thu,  2 Mar 2023 17:35:09 +1000 (AEST)
Received: from freefriends.org (freefriends.org [96.88.95.60])
	by minnie.tuhs.org (Postfix) with ESMTPS id 610E143BE3
	for <tuhs@tuhs.org>; Thu,  2 Mar 2023 17:35:05 +1000 (AEST)
X-Envelope-From: arnold@skeeve.com
Received: from freefriends.org (freefriends.org [96.88.95.60])
	by freefriends.org (8.14.7/8.14.7) with ESMTP id 3227Ylh0014833
	(version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
	Thu, 2 Mar 2023 00:34:48 -0700
Received: (from arnold@localhost)
	by freefriends.org (8.14.7/8.14.7/Submit) id 3227YlJT014832;
	Thu, 2 Mar 2023 00:34:47 -0700
From: arnold@skeeve.com
Message-Id: <202303020734.3227YlJT014832@freefriends.org>
X-Authentication-Warning: frenzy.freefriends.org: arnold set sender to arnold@skeeve.com using -f
Date: Thu, 02 Mar 2023 00:34:47 -0700
To: tuhs@tuhs.org, dave@horsfall.org
References: <20230301150905.AA4CD18C07B@mercury.lcs.mit.edu>
 <alpine.BSF.2.21.9999.2303020714440.4881@aneurin.horsfall.org>
In-Reply-To: <alpine.BSF.2.21.9999.2303020714440.4881@aneurin.horsfall.org>
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID-Hash: T7NKGCQ47YGY3NZCCVZO4QMPENTIDW35
X-Message-ID-Hash: T7NKGCQ47YGY3NZCCVZO4QMPENTIDW35
X-MailFrom: arnold@skeeve.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.6b1
Precedence: list
Subject: [TUHS] Re: Unix v7 icheck dup problem
List-Id: The Unix Heritage Society mailing list <tuhs.tuhs.org>
Archived-At: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/message/T7NKGCQ47YGY3NZCCVZO4QMPENTIDW35/>
List-Archive: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/>
List-Help: <mailto:tuhs-request@tuhs.org?subject=help>
List-Owner: <mailto:tuhs-owner@tuhs.org>
List-Post: <mailto:tuhs@tuhs.org>
List-Subscribe: <mailto:tuhs-join@tuhs.org>
List-Unsubscribe: <mailto:tuhs-leave@tuhs.org>

Dave Horsfall <dave@horsfall.org> wrote:

> On Wed, 1 Mar 2023, Noel Chiappa wrote:
>
> > > I am having a problem clearing a dup inode.
> > 
> > V6 had almost no tools for automagically fixing file system corruption. 
> > To do it, you need to i) understand how the FS works (see:
>
> I could've sworn that I wrote a paper for AUUGN on that very thing, but 
> I'm damned if I can find it...  Anyone here remember it?  It explained 
> exactly how to use icheck/dcheck/ncheck/clri on a creamed file system (and 
> no, I no longer have the document).
>
> -- Dave

So Dave, did you clri the wrong inode such that your lost the paper? :-) :-)