Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!munnari.oz.au!mel.dit.csiro.au!yarra!pta!mcc!chris
From: chris@mcc.oz (Chris Robertson)
Newsgroups: comp.unix.questions
Subject: Re: Recurring problem in root filesystem
Message-ID: <1990Sep11.073849.1716@mcc.oz>
Date: 11 Sep 90 07:38:49 GMT
References: <4010@auspex.auspex.com> <1990Sep04.175054.17770@pilikia.pegasus.com> <4025@auspex.auspex.com> <1990Sep07.184554.27984@pilikia.pegasus.com>
Reply-To: chris@mcc.UUCP (Chris Robertson)
Organization: MCC Software Group
Lines: 15


On some SysV/386's (e.g., Bell Tech 3.2), the system habitually
came up with minor problems in root, even after a clean shutdown.
I came to the conclusion that the system was simply lying when
it said root had been re-mounted after an fsck!  Also, the system
could occasionally get the free space in root so confused that no
amount of taking-it-down-to-single-user-doing-fsck-and-rebooting
worked;  fsck passed with flying colours in single-user mode, then
the no free space problem returned on going mutli-user (so definitely
the root re-mount was not working).  The only fix was to take it
to single user, fsck, then quickly power-fail.  *Then* things came
up clean!  Made me shudder each time I did it, though :-)
-- 
"Down in the dumps?  I TOLD you you'd     |    Chris Robertson
 need two sets..."                        |  chris@mcc.oz