From owner-freebsd-hackers Wed Sep 4 23:32:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA25287 for hackers-outgoing; Wed, 4 Sep 1996 23:32:58 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA25240 for ; Wed, 4 Sep 1996 23:32:26 -0700 (PDT) Received: from root.com (implode.root.com) by mail.crl.com with SMTP id AA09031 (5.65c/IDA-1.5 for ); Wed, 4 Sep 1996 23:30:25 -0700 Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id XAA02686; Wed, 4 Sep 1996 23:29:07 -0700 (PDT) Message-Id: <199609050629.XAA02686@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Jaye Mathisen Cc: Guido van Rooij , FreeBSD-hackers Subject: Re: fsck incorrectly found no errors In-Reply-To: Your message of "Wed, 04 Sep 1996 12:46:31 PDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 04 Sep 1996 23:29:07 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >All I can say is that I have seen the exact same thing, and when it >happens to your 20GB news partition, it sucks the big one. > >I crashed, rebooted, fsck'd 2x, and it crashed regularly with fs >corruption problems. Yet the disks check out fine. > >Once I newfs them, no more problems. (Other than the loss of data). > >Seems to be a problem in fsck I would think. Yes, I think so, too. I noticed that fsck seems to not deal with certain types of directory corruption, for instance, that the kernel detects and panics on. ...I had the same problem a couple of years ago that required newfs'ing the partition to fix. I suppose I should have tried to track the problem down further at that time, but problems like these always happen at the worst times - when you need to get the thing working NOW and have no time to mess with trying to fix the bug(s). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project