Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!mit-eddie!mit-vax!eagle!harpo!utah-cs!utah-gr!thomas
From: thomas@utah-gr.UUCP
Newsgroups: net.bugs.4bsd
Subject: Re: 4.2BSD installation mystery ...
Message-ID: <1014@utah-gr.UUCP>
Date: Wed, 7-Dec-83 21:43:17 EST
Article-I.D.: utah-gr.1014
Posted: Wed Dec  7 21:43:17 1983
Date-Received: Fri, 9-Dec-83 06:42:12 EST
References: <184@rna.UUCP> azure.2397
Lines: 11

The kernel (pre 4.2, anyway) keeps a copy of the superblock for every
mounted filesystem in-core, and only writes it out to the disk i.e., the
disk copy is never reconsulted.  So, if you fsck the raw copy of a
mounted filesystem, and it modifies the superblock, then you are in big
trouble, because what's on the disk doesn't agree with what the kernel
thinks is there.  In 4.1 (and maybe others), you CAN fsck the block
device, as long as the filesystem is "quiescent" (sp?).  I think in
earlier versions, the situation was even worse, but I don't remember the
details now.

=Spencer