Return to BSD News archive
Xref: sserve comp.os.linux:31147 comp.os.386bsd.questions:1040 Newsgroups: comp.os.linux,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!ira.uka.de!news.dfn.de!tubsibr!ramz.ing.tu-bs.de!ruediger From: ruediger@ramz.ing.tu-bs.de (Ruediger Helsch) Subject: fsck bugs (was: Re: 386bsd, linux: which runs more out of the box?) Message-ID: <1993Mar25.171358.20377@ibr.cs.tu-bs.de> Followup-To: <1oqlf5$i8b@agate.berkeley.edu> Keywords: fsck Sender: postnntp@ibr.cs.tu-bs.de (Mr. Nntp Inews Entry) Organization: Mechanikzentrum, Technische Universitaet Braunschweig, Germany References: <1oqlf5$i8b@agate.berkeley.edu> Date: Thu, 25 Mar 1993 17:13:58 GMT Lines: 18 curtis@cs.berkeley.edu (Curtis Yarvin) writes: |> My guess, in fact, is that the bug is in fsck (and efsck, which is |> based on fsck). The "standard" SLS system doesn't run fsck on boot, |> so it's not surprising that there have been few such bug reports; |> I think we might see a lot more if Peter got round to putting a decent |> shutdown/rc package in SLS. I had many problems with fsck; it did not seem to repair anything. This continued until I read the manual pages and found that the flag -r must be used with fsck, else it checks the filesytem but does not repair anything. I was in the good belief of repairing my filesystems after each crash, but instead they were getting more broken every time until they were unrepairable. This behaviour of fsck is different from every other fsck on any other system I used, and probably the reason for quite a lot of severe file system crashes. Ruediger Helsch <ruediger@ramz.ing.tu-bs.de>