Date: Mon, 25 Nov 2002 14:04:58 -0800 From: Terry Lambert <tlambert2@mindspring.com> 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 Message-ID: <3DE29E8A.D226B151@mindspring.com> References: <200211250959.39594.mi%2Bmx@aldan.algebra.com> <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> <20021125172445.GA8953@rot13.obsecurity.org> <200211251254.26497.mi%2Bmx@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DE29E8A.D226B151>