From: "Ron Natalie" <ron@ronnatalie.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>, tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Wed, 01 Mar 2023 16:18:59 +0000 [thread overview]
Message-ID: <em4ba758d8-5579-481a-9867-7b6055491551@ad99ed46.com> (raw)
In-Reply-To: <20230301150905.AA4CD18C07B@mercury.lcs.mit.edu>
You had adb? They hadn’t even released that when we were fixing
things up. If we had a mountable disk that got too corrupt to fix
using the tools, we usually wrote our own and fixed the disk (all our
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
college to be able to be quizzed on just how the (then version 6)
filesystem was layed out and what the possible corruptions were and how
to fix them.
The original V6 filesystem was pretty ugly in that it wasn’t careful in
even trying to do operations in the right order so as not to lead to
hideous corruptions (duplicated blocks etc…). One of our summer
projects at the BRL when we were interning up there was that one of us
(not me) was to write an automatic disk fixer (I had a different
project). Bob never got too far with that.
Clri was especially problematic as a tool. If you wanted to zap a node
that was a 0..0 (i.e., with a zero reference count AND not in any
directory referneces), it would irreverably write zeros over all of it.
We changed it to “clam” which only zonked the mode bits which if you
did it to the wrong inode, you could usually get back to some working
state.
Running icheck and dcheck were standard on reboots. ncheck was pretty
darned slow and we used it mostly for hunting down file names for things
we knew were corrupted and relinking chunks of the filesystem that got
detached from the root.
The world changed when we got better file system code and fsck.
next prev parent reply other threads:[~2023-03-01 16:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:09 Noel Chiappa
2023-03-01 16:18 ` Ron Natalie [this message]
2023-03-01 16:45 ` KenUnix
2023-03-01 16:57 ` Theodore Ts'o
2023-03-01 20:52 ` Dave Horsfall
2023-03-02 1:46 ` Jonathan Gray
2023-03-02 3:05 ` Dave Horsfall
2023-03-02 7:56 ` John Cowan
2023-03-02 8:53 ` Steve Nickolas
2023-03-02 8:01 ` Jonathan Gray
2023-03-02 7:34 ` arnold
2023-03-01 21:29 Noel Chiappa
2023-03-01 21:54 ` KenUnix
2023-03-01 21:55 ` John Cowan
2023-03-01 22:15 ` Jon Forrest
2023-03-02 4:16 ` Jonathan Gray
2023-03-02 1:36 Noel Chiappa
2023-03-02 1:56 ` John Cowan
2023-03-02 6:41 ` Lars Brinkhoff
2023-03-02 2:12 ` Bakul Shah
2023-03-02 2:46 ` Rich Salz
2023-03-02 1:59 Noel Chiappa
2023-03-02 2:11 ` Dan Cross
2023-03-03 18:22 Noel Chiappa
2023-03-03 19:25 ` Chet Ramey
2023-03-03 21:26 ` John Cowan
2023-03-04 0:23 ` Chet Ramey
2023-03-03 19:35 ` Clem Cole
2023-03-04 2:45 ` Jonathan Gray
2023-03-03 23:00 ` Jonathan Gray
2023-03-04 9:07 ` Jonathan Gray
2023-03-04 11:19 ` KenUnix
2023-03-04 14:41 Noel Chiappa
2023-03-04 14:49 ` KenUnix
2023-03-06 8:14 Noel Chiappa
2023-03-06 8:58 ` Jonathan Gray
2023-03-07 2:05 ` Kenneth Goodwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em4ba758d8-5579-481a-9867-7b6055491551@ad99ed46.com \
--to=ron@ronnatalie.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).