Date: Tue, 26 Dec 2006 22:47:25 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Geoffrey Giesemann <geoffwa@cs.rmit.edu.au> Cc: stable@freebsd.org Subject: Re: Background fsck causes kernel panic Message-ID: <20061227034724.GB9859@xor.obsecurity.org> In-Reply-To: <20061226225411.GA8706@cs.rmit.edu.au> References: <20061226225411.GA8706@cs.rmit.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--UHN/qo2QbUvPLonB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Dec 27, 2006 at 09:54:11AM +1100, Geoffrey Giesemann wrote: > Running a fairly recent RELENG_6 SMP kernel, I had a nasty experience > where filesystem corruption on a pair of RAID5 volumes on an arcmsr > would cause the machine to panic during the background fsck. This > resulted in a merry crash-reboot-crash cycle until I booted on to an > install CD, ran a foreground fsck and fixed the errors. Yes, this is the danger when running bg fsck and your system experiences a panic or other non-softupdates-safe source of filesystem corruption. As you discovered, the solution is to force a fsck to repair all corruption and then proceed (optionally disabling bg fsck permanently to prevent a recurrence ;-) Kris --UHN/qo2QbUvPLonB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFkezMWry0BWjoQKURAuhXAJ0VYk/8NHbsqeUZez13yyL/ctN5FACg/Ta3 Lzg1sj2NF5/GxpQxvlUDtlQ= =AosZ -----END PGP SIGNATURE----- --UHN/qo2QbUvPLonB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061227034724.GB9859>