From owner-freebsd-current Mon Nov 25 14: 4:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5089B37B442; Mon, 25 Nov 2002 14:04:05 -0800 (PST) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2DCC43E9C; Mon, 25 Nov 2002 14:04:04 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0340.cvx40-bradley.dialup.earthlink.net ([216.244.43.85] helo=mindspring.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18GRKH-0006Ci-00; Mon, 25 Nov 2002 14:03:33 -0800 Message-ID: <3DE29DE6.CDD96F3F@mindspring.com> Date: Mon, 25 Nov 2002 14:02:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Robert Watson , Mikhail Teterin , current@FreeBSD.ORG Subject: Re: -current unusable after a crash References: <200211250959.39594.mi+mx@aldan.algebra.com> <20021125172445.GA8953@rot13.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message