Path: utzoo!utgpu!jarvis.csri.toronto.edu!neat.cs.toronto.edu!lamy
Newsgroups: comp.sys.mips
From: lamy@ai.utoronto.ca (Jean-Francois Lamy)
Subject: Re: root file system not checked on reboot
Message-ID: <89Aug1.213306edt.10423@neat.cs.toronto.edu>
References: <4529@watvlsi.waterloo.edu> <24497@abbott.mips.COM>
Distribution: comp
Date: 2 Aug 89 01:34:05 GMT

Our SGI 4d/240 just did similar deeds (SysV admin stuff, like the MIPS).  Root
was fscked, machine rebooted.  fsck of root is skipped, even though it is in
fact still corrupt.  /usr is then found dirty, machine fsck's it.  The reset
button is pressed, the machine reboots. Both root and /usr fscks are skipped,
except both are still corrupt.

The people who came up with this brilliant scheme apparently have never seen a
partition that requires 3 fscks before being coming out clean.  We will most
likely put in a good old forced fsck of root and usr no matter what, and find
a way to prevent the machine from going multi-user when anything but the most
minor damage is repaired.

This likely belongs in comp.bugs.sys5

Jean-Francois Lamy               lamy@ai.utoronto.ca, uunet!ai.utoronto.ca!lamy
AI Group, Department of Computer Science, University of Toronto, Canada M5S 1A4