From owner-freebsd-hackers@FreeBSD.ORG Mon May 2 02:53:07 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B9CD16A4CE for ; Mon, 2 May 2005 02:53:07 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id E27CD43D1D for ; Mon, 2 May 2005 02:53:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2E773513B1; Sun, 1 May 2005 19:53:06 -0700 (PDT) Date: Sun, 1 May 2005 19:53:06 -0700 From: Kris Kennaway To: Steven Hartland Message-ID: <20050502025305.GA29984@xor.obsecurity.org> References: <007901c54ec0$14bb3e30$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <007901c54ec0$14bb3e30$b3db87d4@multiplay.co.uk> User-Agent: Mutt/1.4.2.1i cc: freebsd-hackers@freebsd.org Subject: Re: 5.4-STABLE corrupting fs on shutdown -p now? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2005 02:53:07 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 02, 2005 at 03:38:49AM +0100, Steven Hartland wrote: > Seems like doing a shutdown -p now on the current > 5.4-STABLE branch is resulting in FS corruption. > I've done this 4 times now and all but 1 time the > machine has failed to boot with a panic: > mod=3D0100600, inum=3D1271817, fs=3D/var > panic: ffs_valloc: dup alloc > cpuid =3D 0 > boot() called on cpu#0 >=20 > The only way to fix is single user mode and manually > run fsck. Even the one time it didn't cause a panic I > still got a warning about / not being clean which it > should have been as the machine shutdown cleanly > no outstanding buffers. In some cases fsck will not repair all corruption in one pass. Rerun it until it stops finding new things to fix. > Could this change have something to do with the panic > happening instead of just recovering? Doesn't seem likely to me. > Why would FS's be being corrupted by "shutdown -p now" where > as "reboot" doesnt seem to? Maybe the machine is being powered down before your disks have finished writing their data to disk. Kris --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCdZYRWry0BWjoQKURApy+AKD7O8Wj6afnRrLdqQj+k7zDHk9sNQCeIoXv MXLJUg/8UxbWjBqKRbCFTCI= =re3X -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--