Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!convex!cs.utexas.edu!uunet!pipex!uknet!mcsun!sun4nl!hacktic!hacktic!not-for-mail From: cor@hacktic.nl (Cor) Newsgroups: comp.os.386bsd.questions Subject: Re: fsck summary info bad after every shutdown Date: 18 May 1993 15:06:21 +0200 Organization: Hack-Tic, networking for the masses Lines: 24 Message-ID: <1tan0rINN2f5@xs4all.hacktic.nl> References: <root.737640955@gimli> NNTP-Posting-Host: xs4all.hacktic.nl root@gimli.cs.uct.ac.za (Sandi Donno) writes: >Has anyone had the following problem, or can anyone point me at the >likely cause: >I have installed 386bsd on 4 identical 486's with 120MB IDE hard drives, and >patchkit 0.2.3. Whether I use /sbin/shutdown, /usr/distbin/shutdown or reboot, >fsck always finds the summary information bad after rebooting; the system >is rebooted and the next time fsck finds no errors. I dont really have that problem, but I do have a problem with fsck It has happened twice sofar that fsck gives me a memory fault and dumps core, which is not fun when your filesystem is corrupt. I had to manually remove the inodes of the files causing the memory fault (usually big directories) and try again. Maybe a bug somewhere in fsck? cor -- | cor@hacktic.nl | Hack-Tic System Mismanagement | +31-20-6001480-3 (VMB) | | -------------------------------------------------------------------------| | ######### Signature Virus Running. Contamination Complete ######### | +--------------------------------------------------------------------------+