From owner-freebsd-current  Mon Nov 25  9:51:29 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 019D437B401; Mon, 25 Nov 2002 09:51:27 -0800 (PST)
Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9241843EAA; Mon, 25 Nov 2002 09:51:26 -0800 (PST)
	(envelope-from mi+mx@aldan.algebra.com)
Received: from misha.murex.com (250-217.customer.cloud9.net [168.100.250.217])
	by corbulon.video-collage.com (8.12.6/8.12.6) with ESMTP id gAPHpNjJ006486
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL);
	Mon, 25 Nov 2002 12:51:25 -0500 (EST)
	(envelope-from mi+mx@aldan.algebra.com)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Mikhail Teterin <mi+mx@aldan.algebra.com>
Organization: Virtual Estates, Inc.
To: Kris Kennaway <kris@obsecurity.org>,
	Robert Watson <rwatson@FreeBSD.ORG>
Subject: Re: -current unusable after a crash
Date: Mon, 25 Nov 2002 12:54:26 -0500
User-Agent: KMail/1.4.3
Cc: current@FreeBSD.ORG
References: <200211250959.39594.mi+mx@aldan.algebra.com> <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> <20021125172445.GA8953@rot13.obsecurity.org>
In-Reply-To: <20021125172445.GA8953@rot13.obsecurity.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200211251254.26497.mi+mx@aldan.algebra.com>
X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang)
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

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?

= I've seen far too much bizarre filesystem behaviour that went away the
= next time I did a full fsck.

	-mi


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