Adrian Chadd wrote:
> On Thu, Jun 22, 2000, Julian Elischer wrote:
> [snip NetBSD making softupdates a mount option]
> > They obvioulsly DIDN'T discuss this with Kirk!
> > 
> > this is not what he wants and for good reason..
> > see the long discussion son this topic in the archives.
> I've read the mail archives as to why. If these issues are still
> valid, I'll withdrawl the idea :)

Because fsck is supposed to be able to do things more intelligently when it
knows the *previous* mount state, not the current state.  ie: if a disk was
last mounted in softupdates mode, fsck is supposed to do stuff differently
(possibly doing as little as a superblock cleanup and deferring the
lost-space recovery until much later).

For the NetBSD version to work, what needs to happen is that the -osoftdep
flag needs to be propagated to the superblock so that after reboot, fsck
knows what to do.  When it is next mounted, then update it to the new state.

This gives us the ability to use the 'softdep' flag in fstab but without
breaking fsck.

Sure, fsck can look at what is *now* in fstab, but not what mode a given
filesystem was in the last time it was mounted.

"All of this is for nothing if we don't go to the stars" - JMS/B5

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to