Xref: utzoo comp.sys.att:6392 unix-pc.general:2873
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!emory!dtscp1!gbmatl!gbm
From: gbm@gbmatl.UUCP (gary mckenney)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: 3b1 40meg disk woes: Help
Message-ID: <1763@gbmatl.UUCP>
Date: 7 May 89 17:52:44 GMT
References: <3961@emory.mathcs.emory.edu} <17513@cup.portal.com> <2947@ihuxy.ATT.COM> <586@cbnewsc.ATT.COM> <17733@cup.portal.com> <1989May5.150438.13740@ziebmef.uucp> <480@becker.UUCP>
Reply-To: gbm@gbmatl.UUCP (Root)
Organization: Atlanta Programming & Consulting, Inc.
Lines: 19

In article <480@becker.UUCP} bdb@becker.UUCP (Bruce Becker) writes:
}In article <1989May5.150438.13740@ziebmef.uucp> cks@ziebmef.UUCP (Chris Siebenmann) writes:
}
}	I have never run up against the problem, even though
}	I've had the machine up for months at a time, with
}	*lots* of disk activity - news & many uucp connections
}	exercise a disk drive & file system pretty good.
}	The main problem seems to be that fsck *always* runs
}	twice at reboot time. I'm not sure why that is, but I
}	seem to recall that it did not happen "at the beginning",
}	but started happening fairly early on.
}	Also, the quota system has never worked 8^) - I guess
}	that 2nd drive will help whenever the interface is up
}	& running...

According to the rc script in /etc fsck will force a reboot and therefore a
second fsck if it finds problems through the first fsck.  In other words if
there is a permenent problem found by fsck I don't think you will be able
to boot up your machine.