Subject: Re: bin/1219: [dM] fsck is too aggressive about clean flags
To: Peter Seebach <seebs@solon.com>
From: Chris G Demetriou <Chris_G_Demetriou@BALVENIE.PDL.CS.CMU.EDU>
List: netbsd-bugs
Date: 07/13/1995 11:27:21
> Just for reference, I've decided that mount is too lax about
> dirty flags; on a change to multi-user, the system just complains that
> all the filesystems are dirty - but still mounts them! Since you can't umount
> /usr ("device busy"), you then have to hard boot immediately to recover
> usefully, ... see, copying a kernel to /dev/reload syncs disks.
(1) on a change to multi-user, why are your file systems _ever_ dirty?
if booting to multi-user, rc should be checking your disks. if
going from single-user, your disks should have previously been
checked, or you should make sure that you've fsck'd them yourself.
(2) have you tried using 'mount -u' to update the mount information?
there is an undocumented mount option 'reload' which causes file
system buffers to be flushed and reloaded from disk. you should
be able to forcibly update-mount /usr read-only, then reload and
update-mount it read-write.
cgd