Date: Mon, 25 Nov 2002 09:24:45 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Mikhail Teterin <mi+mx@aldan.algebra.com>, current@FreeBSD.ORG Subject: Re: -current unusable after a crash Message-ID: <20021125172445.GA8953@rot13.obsecurity.org> In-Reply-To: <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> References: <200211250959.39594.mi%2Bmx@aldan.algebra.com> <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE94lzcWry0BWjoQKURAmm5AKC/AOmaamVtegW6bg1ynB+uLTqJVACfU7H7 M+C5bMOVYNg0rbH8s7+SR4g= =1q1o -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021125172445.GA8953>