From owner-freebsd-current Mon Jan 27 4:11: 4 2003 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 8C80A37B401; Mon, 27 Jan 2003 04:11:03 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id D953043E4A; Mon, 27 Jan 2003 04:11:02 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h0RCAx2E001153; Mon, 27 Jan 2003 04:10:59 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h0RCAwiG001152; Mon, 27 Jan 2003 04:10:58 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Mon, 27 Jan 2003 04:10:58 -0800 From: David Schultz To: Greg Lehey Cc: Andy Farkas , Thomas David Rivers , Robert Watson , current@FreeBSD.ORG Subject: Re: I've just had a massive file system crash Message-ID: <20030127121058.GC388@HAL9000.homeunix.com> Mail-Followup-To: Greg Lehey , Andy Farkas , Thomas David Rivers , Robert Watson , current@FreeBSD.ORG References: <20030124093754.GD2402@sydney.worldwide.lemis.com> <20030124093754.GD2402@sydney.worldwide.lemis.com> <200301241153.h0OBrf654388@lakes.dignus.com> <20030124093754.GD2402@sydney.worldwide.lemis.com> <20030124203116.H62832-100000@hewey.af.speednet.com.au> <20030125043817.GD929@sydney.worldwide.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030125043817.GD929@sydney.worldwide.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Greg Lehey : > I've been thinking about what happened, and I have a possibility: the > session before shutdown included a lot of writing to that file system, > and I did a shutdown -p. It's possible that the shutdown powered off > the system before the disk had flushed its cache. For the moment I'm > avoiding shutdown -p, but when I get home I'll try to provoke it > again. Just a heads up: Soeren tells me he will commit a fix for this in his next ATA meta-commit. I have patches if wanted. I still can't figure out why the problem would trash your entire home directory, though. Even if the disk reordered writes and failed to write some sectors, directory entries that were not being actively modified shouldn't have become corrupted, as far as I know. (Maybe your disk does track-at-once writes and just happened to be flushing the last few sectors from its cache when the power was cut.) Perhaps someone could ask Kirk, although it may take an actual hosed filesystem to diagnose what happened. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message