From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: Jonathan Gray <jsg@jsg.id.au>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Mon, 6 Mar 2023 21:05:13 -0500 [thread overview]
Message-ID: <CAMQbRb1oVtS=AA=dfQC1M_T3f66M4wy=Lkai40rRF0DxnA6sXQ@mail.gmail.com> (raw)
In-Reply-To: <ZAWrTtlU/ALZIHZL@largo.jsg.id.au>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
Anyone remember PFSCK, aka parallel fsck that fired up multiple parallel
fsck instances, one per filesystem and used bidirectional pipes to pass
commands from the operator to each individual fsck stream. Cut boot times
down quite a bit on healthy systems.
I believe the filesystem MOUNT table file on ROOT had fields related to
controlling PFSCK behavior
I remember hacking it for some reason related to performance, But GOK
why......
On Mon, Mar 6, 2023, 3:59 AM Jonathan Gray <jsg@jsg.id.au> wrote:
> On Mon, Mar 06, 2023 at 03:14:27AM -0500, Noel Chiappa wrote:
> >
> > I've also been amusing myself trying to figure out who wrote:
> >
> > http://ana-3.lcs.mit.edu/~jnc/tech/unix/s1/fcheck.c
>
> According to Guy Harris in
> https://groups.google.com/g/net.unix/c/-H9x36DMOBQ/m/4mcL76lKbmMJ
>
> 'they had to replace "icheck" and "dcheck" with a new program which
> would do most of the dirty work of file system repair for them -
> Hal wrote one called "fcheck", which cleaned V6 file systems, and
> which appeared in source-code form on the PWB/UNIX 1.0 distribution
> tape. Unfortunately, PWB/UNIX 1.0 modified the V6 file system so
> that it didn't support "huge" files, and the eighth indirect pointer
> pointed directly to a block as the other seven did, so the "fcheck"
> there wouldn't fix a vanilla PWB/UNIX file system, but it worked
> just fine on a vanilla V6 FS.'
>
[-- Attachment #2: Type: text/html, Size: 2122 bytes --]
next prev parent reply other threads:[~2023-03-07 2:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 8:14 Noel Chiappa
2023-03-06 8:58 ` Jonathan Gray
2023-03-07 2:05 ` Kenneth Goodwin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 14:41 Noel Chiappa
2023-03-04 14:49 ` KenUnix
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-02 1:59 Noel Chiappa
2023-03-02 2:11 ` Dan Cross
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-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-01 15:09 Noel Chiappa
2023-03-01 16:18 ` Ron Natalie
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
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='CAMQbRb1oVtS=AA=dfQC1M_T3f66M4wy=Lkai40rRF0DxnA6sXQ@mail.gmail.com' \
--to=kennethgoodwin56@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=jsg@jsg.id.au \
--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).