From owner-freebsd-current  Mon Nov 25 14: 6:43 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 74BFE37B401; Mon, 25 Nov 2002 14:06:42 -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 62F6043EE6; Mon, 25 Nov 2002 14:06:41 -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 18GRMu-0002MO-00; Mon, 25 Nov 2002 14:06:17 -0800
Message-ID: <3DE29E8A.D226B151@mindspring.com>
Date: Mon, 25 Nov 2002 14:04:58 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mikhail Teterin <mi+mx@aldan.algebra.com>
Cc: Kris Kennaway <kris@obsecurity.org>,
	Robert Watson <rwatson@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: -current unusable after a crash
References: <200211250959.39594.mi+mx@aldan.algebra.com> <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> <20021125172445.GA8953@rot13.obsecurity.org> <200211251254.26497.mi+mx@aldan.algebra.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Mikhail Teterin wrote:
> On Monday 25 November 2002 12:24 pm, 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.
> 
> Otherwise, is there a need for fsck at all? Can sudden powerloss be
> reliably distinguished from a panic?

No, nor from hardware failures (disk/controller/other), without
NVRAM to save the crash reason in the case there is one.

-- Terry

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