Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!dogie.macc.wisc.edu!uwvax!heurikon!dklann
From: dklann@heurikon.UUCP (David Klann)
Newsgroups: comp.sys.att
Subject: Re: fsck & 3b1 continuous power up
Keywords: reboot 3b1 7300 fsck fsstat
Message-ID: <331@heurikon.UUCP>
Date: 10 May 89 20:17:41 GMT
References: <1084@adds.newyork.NCR.COM>
Reply-To: dklann@heurikon.UUCP (David Klann)
Followup-To: comp.sys.att
Organization: Heurikon Corp., Madison WI
Lines: 29

In article <1084@adds.newyork.NCR.COM> tanya@adds.newyork.NCR.COM (Tanya Katz) writes:
>
>   [ Discussion about /etc/rc running fsck... ]
>
>Any Comments??
>
>Tanya
>
Tanya (and others),

I leave my 7300 on full time (with the exception of week-long vacations,
etc.).  I have removed the call to fsck from my /etc/rc.  To me, it is
silly to run fsck like that when booting.  To get around file system
problems I simply run fsck from the command line.  I have yet (over a
year) to find any major problems.

It's too bad the UNIXpc kernel doesn't have/make use of the s_state field in
the super-block.  That would increase the certainty about the state of
the root file system when booting.  I'd love to set the file system
state to "FsOKAY" as the last thing before shutting the system down.  In
fact I think I'll look into that very thing.  That's it!  All we need is
a pair of utilities, one to set it, and a version of fsstat to check it.
I'll post them if/when they're working...

Comments?  Flames?

David Klann
Heurikon Corporation
{backbone}!uwvax!heurikon!dklann