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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 743 invoked from network); 1 Mar 2023 16:19:14 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 1 Mar 2023 16:19:14 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 2670E4332A; Thu, 2 Mar 2023 02:19:08 +1000 (AEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by minnie.tuhs.org (Postfix) with ESMTPS id 591AF43329 for ; Thu, 2 Mar 2023 02:19:01 +1000 (AEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 8CB123200488; Wed, 1 Mar 2023 11:19:00 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 01 Mar 2023 11:19:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ronnatalie.com; h=cc:cc:content-transfer-encoding:content-type:date:date:from :from:in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:reply-to:sender:subject:subject:to:to; s=fm3; t= 1677687540; x=1677773940; bh=ECQXBw4ZrpyGlfkrrF3dDOWJdS34fejHYA/ BGfexHG0=; b=Ikk9WDweVdsm/obeEsg6kskdAncGvdriXZYTieHrAFUftXXDUcc WywqiQK1INunYC1FIT4QWJrH3/RQh68c/ir3YMJ0ImE8Yss5812BDhqTXHjisYes kcB08fuExT6cjqqTFEOecyCavZUtb9NFh5hLC+8cv3DhsKT+JgF3K1peV++L5DYC sR2S07Je8ELCP1vtgRjShkyFJ5HbDS1b4iaQhzJvWCw4lX/6BeEcFKpRAs7VDaJL drK2OLLsTmyYz5IzviqPwud83WDu8yQQBnRVNy0kAZ6AXc/Eb91i69t7mtICUW70 pcWpGCyo4mG50AMxilLGelH8dzpz4xqsKXg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1677687540; x=1677773940; bh=ECQXBw4ZrpyGlfkrrF3dDOWJdS34fejHYA/ BGfexHG0=; b=WsjnSH7c9EHhJs8SrneNGtz7HmHdoRY2zaGf4Oq+bQW98U+mGRb mWJq4yCSKHOftwuMfkLQzrDn7rNcT4lRN60/YyIIM1D9YLO+Mz8iAPPIQh7L80Z2 Csa4SDPSJBU/WVF1KnEI6OTqwd/HuKP5Bwkekv+YmLXEH9+lDDhlaklYfvXSxABw rk5WTh51iCzJttraqlMxjPCgbpqnAMmRNTcBMD6KOCW+PpbtN4qs4zeUv9kG3zV0 /7ldfCqZCS7Z6vNzpNBJ4srJvVDpQLz1tISKjMrhU1GAQ1xsRHNNL1s8gq5KTemB 4Ewyg51ksqzSyjdnL61Jug0g03FmwYy8x+A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelhedgjeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffuveffkfgjfhhrfgggtgfgse htqhertddtreejnecuhfhrohhmpedftfhonhcupfgrthgrlhhivgdfuceorhhonhesrhho nhhnrghtrghlihgvrdgtohhmqeenucggtffrrghtthgvrhhnpeduieeifefgtdffgfejue evleeihfehueejvedufeelfeejtdehjeeugfduhfdukeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehrohhnsehrohhnnhgrthgrlhhivgdrtg homh X-ME-Proxy: Feedback-ID: iaba146ad:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Mar 2023 11:18:59 -0500 (EST) From: "Ron Natalie" To: "Noel Chiappa" , tuhs@tuhs.org Date: Wed, 01 Mar 2023 16:18:59 +0000 Message-Id: In-Reply-To: <20230301150905.AA4CD18C07B@mercury.lcs.mit.edu> References: <20230301150905.AA4CD18C07B@mercury.lcs.mit.edu> User-Agent: eM_Client/9.2.1608.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Message-ID-Hash: F7JLWRVP5OHKX664BMFCGNKFC2IPGTZO X-Message-ID-Hash: F7JLWRVP5OHKX664BMFCGNKFC2IPGTZO X-MailFrom: ron@ronnatalie.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 CC: jnc@mercury.lcs.mit.edu X-Mailman-Version: 3.3.6b1 Precedence: list Reply-To: Ron Natalie Subject: [TUHS] Re: Unix v7 icheck dup problem List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: You had adb? They hadn=E2=80=99t even released that when we were fixing= =20 things up. If we had a mountable disk that got too corrupt to fix=20 using the tools, we usually wrote our own and fixed the disk (all our=20 packs in those days were pretty much RK05s) from a running sytsem. It was reqiured before you could come on the operations staff at my=20 college to be able to be quizzed on just how the (then version 6)=20 filesystem was layed out and what the possible corruptions were and how=20 to fix them. The original V6 filesystem was pretty ugly in that it wasn=E2=80=99t carefu= l in=20 even trying to do operations in the right order so as not to lead to=20 hideous corruptions (duplicated blocks etc=E2=80=A6). One of our summer= =20 projects at the BRL when we were interning up there was that one of us=20 (not me) was to write an automatic disk fixer (I had a different=20 project). Bob never got too far with that. Clri was especially problematic as a tool. If you wanted to zap a node=20 that was a 0..0 (i.e., with a zero reference count AND not in any=20 directory referneces), it would irreverably write zeros over all of it. =20 We changed it to =E2=80=9Cclam=E2=80=9D which only zonked the mode bits= which if you=20 did it to the wrong inode, you could usually get back to some working=20 state. Running icheck and dcheck were standard on reboots. ncheck was pretty=20 darned slow and we used it mostly for hunting down file names for things=20 we knew were corrupted and relinking chunks of the filesystem that got=20 detached from the root. The world changed when we got better file system code and fsck.