Date: Wed, 04 Sep 1996 23:29:07 -0700 From: David Greenman <dg@root.com> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: Guido van Rooij <guido@gvr.win.tue.nl>, FreeBSD-hackers <FreeBSD-hackers@freebsd.org> Subject: Re: fsck incorrectly found no errors Message-ID: <199609050629.XAA02686@root.com> In-Reply-To: Your message of "Wed, 04 Sep 1996 12:46:31 PDT." <Pine.NEB.3.95.960904124431.436X-100000@mail.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609050629.XAA02686>