From owner-freebsd-stable@FreeBSD.ORG Wed Dec 27 03:47:26 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00C0716A412 for ; Wed, 27 Dec 2006 03:47:26 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E3A8D13C478 for ; Wed, 27 Dec 2006 03:47:25 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BF9EB1A4D81; Tue, 26 Dec 2006 19:47:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 393DE51870; Tue, 26 Dec 2006 22:47:25 -0500 (EST) Date: Tue, 26 Dec 2006 22:47:25 -0500 From: Kris Kennaway To: Geoffrey Giesemann Message-ID: <20061227034724.GB9859@xor.obsecurity.org> References: <20061226225411.GA8706@cs.rmit.edu.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UHN/qo2QbUvPLonB" Content-Disposition: inline In-Reply-To: <20061226225411.GA8706@cs.rmit.edu.au> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org Subject: Re: Background fsck causes kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 03:47:26 -0000 --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--