From owner-freebsd-fs  Mon May 14 14:46: 2 2001
Delivered-To: freebsd-fs@freebsd.org
Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [63.114.185.254])
	by hub.freebsd.org (Postfix) with ESMTP
	id DD62F37B422; Mon, 14 May 2001 14:45:59 -0700 (PDT)
	(envelope-from mi@aldan.algebra.com)
Received: from misha.privatelabs.com (root@misha.plten [10.0.0.106])
	by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id RAA14351;
	Mon, 14 May 2001 17:06:36 -0400
From: mi@aldan.algebra.com
Received: from misha.privatelabs.com (mi@localhost [127.0.0.1])
	by misha.privatelabs.com (8.11.3/8.11.1) with ESMTP id f4ELjrq13574;
	Mon, 14 May 2001 17:45:55 -0400 (EDT)
	(envelope-from mi@aldan.algebra.com)
Message-Id: <200105142145.f4ELjrq13574@misha.privatelabs.com>
Date: Mon, 14 May 2001 17:45:52 -0400 (EDT)
Reply-To: mi@aldan.algebra.com
Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] 
To: mckusick@mckusick.com
Cc: kris@obsecurity.org, ru@FreeBSD.org, fs@FreeBSD.org
In-Reply-To: <200105132342.QAA21879@beastie.mckusick.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On 13 May, Kirk McKusick wrote:
>> > 1) Downgrade the FS to readonly mode.
>> 
>> Can't a foreground  fsck be run at this moment?  Having to reboot for
>> anything is rather ugly... I'm sure there is a reason it can not, I'm
>> just wondering, what that reason is. Thanks!

> Indeed, a foreground  fsck can be run once the  downgrade to read-only
> has happened. However, doing so automatically is unlikely to be useful
> since nearly  every error that  would get us  to this point  will also
> cause an `fsck  -p' to fail. So, at this  point a system administrator
> is going to have to intervene to  do a manual fsck. Once the downgrade
> to read-only has happened, no  further filesystem damage can occur, so
> there is  not a  great rush to  run the manual  fsck. However,  if the
> affected filesystem is something crucial like /var, the system may not
> run at all well until the problem is fixed.

So, Kris' proposition to keep rebooting is not really good either...

Perhaps, fsck  needs to be  modified to do the  logging by itself  -- on
different levels and priorities instead of relying on the logger?

	-mi



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message