Kris Kennaway wrote: > On Mon, Nov 25, 2002 at 10:24:46AM -0500, Robert Watson wrote: > > > I thought, this might be due to the priority of the background fsck and > > > have once left it alone for several hours -- with no effect. The usual > > > fsck takes a few minutes. > > We really need to disable background fsck if the system panicked. > I've seen far too much bizarre filesystem behaviour that went away the > next time I did a full fsck.
I don't think this is really possible. I went looking for a generic "application use" CMOS are for this sort of thing a while back, and I was unable to find one. If you made system dumps mandatory (or marked swap with a non-dump header in case of panic), this still would not handle the "silent reboot", "double panic", or "single panic with disk I/O trashed" cases. 8-(. There was a discussion about these issues when background fsck first went in. My opinion of having it on by default is that if you are going to play that loose, you might as well mount the FSs async, and be done with it. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
