Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!apple!vsi1!wyse!mips!rogerk
From: rogerk@mips.COM (Roger B.A. Klorese)
Newsgroups: comp.sys.mips
Subject: Re: root file system not checked on reboot
Message-ID: <24567@abbott.mips.COM>
Date: 2 Aug 89 20:01:18 GMT
References: <4529@watvlsi.waterloo.edu> <24497@abbott.mips.COM> <4533@watvlsi.waterloo.edu>
Reply-To: rogerk@mips.COM (Roger B.A. Klorese)
Organization: MIPS Computer Systems, Sunnyvale, CA
Lines: 20

In article <4533@watvlsi.waterloo.edu> jabarby@watvlsi.waterloo.edu (Jim Barby) writes:
>In article <24497@abbott.mips.COM>, rogerk@mips.COM (Roger B.A. Klorese) writes:
>> The logic seems to be that the only way to have a damaged filesystem if it
>> was dismounted cleanly would be if something scribbled on the unmounted
>> device file.
>Roger, is the root filesystem not an unmounted filesystem (ie always
>there)?  If so, the above logic just does not wash.

I agree.  I was just explaining the logic in the code.  I believe that it
is not sufficiently pessimistic.  In fact, the special check for root is
simply "is it not marked clean"; I'm not sure this can ever not be the case.

We are looking for solutions.  We believe we have a general improvement in 
mind for fsck at startup, but it is early to tell if it will make it into
the next major release.
-- 
ROGER B.A. KLORESE      MIPS Computer Systems, Inc.      phone: +1 408 720-2939
928 E. Arques Ave.  Sunnyvale, CA  94086                        rogerk@mips.COM
{ames,decwrl,pyramid}!mips!rogerk
"I want to live where it's always Saturday."  -- Guadalcanal Diary