From owner-freebsd-current  Mon Dec  9 19: 9:55 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5C61F37B401
	for <current@freebsd.org>; Mon,  9 Dec 2002 19:09:54 -0800 (PST)
Received: from beastie.mckusick.com (217-saunders-pool.towerstream.com [198.31.184.217])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2834443EA9
	for <current@freebsd.org>; Mon,  9 Dec 2002 19:09:53 -0800 (PST)
	(envelope-from mckusick@beastie.mckusick.com)
Received: from beastie.mckusick.com (localhost [127.0.0.1])
	by beastie.mckusick.com (8.12.3/8.12.3) with ESMTP id gBA39h59001465;
	Mon, 9 Dec 2002 19:09:43 -0800 (PST)
	(envelope-from mckusick@beastie.mckusick.com)
Message-Id: <200212100309.gBA39h59001465@beastie.mckusick.com>
To: Nate Lawson <nate@root.org>
Subject: Re: Data corruption in soft updates? 
Cc: current@freebsd.org
In-Reply-To: Your message of "Mon, 09 Dec 2002 18:04:03 PST."
             <Pine.BSF.4.21.0212091744550.26237-100000@root.org> 
Date: Mon, 09 Dec 2002 19:09:43 -0800
From: Kirk McKusick <mckusick@beastie.mckusick.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

	Date: Mon, 9 Dec 2002 18:04:03 -0800 (PST)
	From: Nate Lawson <nate@root.org>
	To: current@freebsd.org
	cc: mckusick@mckusick.com
	Subject: Data corruption in soft updates?
	X-ASK-Info: Whitelist match

	I rebuilt my kernel with today's current + the acpica-20021122
	patch and rebooted.  I use ufs1, no acls or special options
	other than SU (installed with DP1).  Everything booted fine
	with some errors from acpi but as booting proceeded, I
	started getting kernel messages of "bad inode".  I quickly
	rebooted to single user and ran fsck and got a huge set of
	errors.  See this partial log (600KB gzipped):

	   http://www.root.org/~nate/fsck.gz

	I didn't touch all those files (just booted and started
	getting errors) so I don't want to say "yes" to deleting
	them.  Do I have to newfs/reinstall?  Should I try using a
	superblock backup?

	-Nate

It appears that you are getting all those errors (BAD block)
because fsck thinks that your filesystem is smaller than it
really is. If you do a dumpfs on the filesystem and check
the size (about line 5), I expect that you will find that
all those bad blocks exceed that size. It might be interesting
to check one or more of the alternate blocks to see if they
have a different size. If so, using an alternate should help.
If not, then the question is why all those out of range blocks 
were allocated.

	Kirk McKusick

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message