From owner-freebsd-current Mon Jan 27 15:18:55 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 9C72437B401; Mon, 27 Jan 2003 15:18:54 -0800 (PST) Received: from papagena.rockefeller.edu (papagena.rockefeller.edu [129.85.41.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id D59C743E4A; Mon, 27 Jan 2003 15:18:53 -0800 (PST) (envelope-from rsidd@papagena.rockefeller.edu) Received: (from rsidd@localhost) by papagena.rockefeller.edu (8.11.6/8.11.6) id h0RNIkm28268; Mon, 27 Jan 2003 18:18:46 -0500 Date: Mon, 27 Jan 2003 18:18:46 -0500 From: Rahul Siddharthan To: David Schultz Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: I've just had a massive file system crash Message-ID: <20030127181846.G26719@papagena.rockefeller.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030127121058.GC388@HAL9000.homeunix.com> X-Operating-System: Linux 2.4.9-12smp i686 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 David Schultz wrote: > 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. Something similar happened to me in 4-STABLE several months ago. After a panic/crash (caused by an unstable USB audio driver) the automatic fsck failed. This happened twice; the second time my filesystem was totally messed up, and after fsck did its thing, several files were missing, including files in /usr/bin and /usr/sbin that had not been touched for many weeks (ie since the last installworld). The damage wasn't as extensive as Greg reports, and my home directory was spared, but I had to reinstall the base system to get things working smoothly again. I then turned off write caching on the IDE drive. Afterwards I had several such crashes (caused by the same driver) but never again had filesystem damage -- automatic fsck always worked. Nevertheless, as you say, it's strange files which had not been touched went missing. - Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message