disk inconsistency - should 'fsck' always executed with -y ?

[gaf at blu.org (Jerry Feldman)]

What I meant was that if you have a drive with a lot of errors, it might be 
indicative of a failing drive. If you have your system set up for automatic 
recovery, you might not know about a problem until you've lost the drive. 
Log files tell the story only if you look at them. Also, if fsck makes 
changes to the root file system, you will need to reboot. fsck is normally 
run on unmounted file systems which do not require a reboot when 
modified, so you  really want to make sure everything is performed in 
such a manner as to recover your file system as best as possible without 
making the problem worse. If you want a thorough fsck during boot, you 
probably also want the script to force a reboot if fsck fixes an error since 
you have one partition. 

On 2 Feb 2001, at 13:38, Glenn Burkhardt wrote:

> > It is simply when there is a serious problem, you might want 
> > a human to take a look at it. 
> 
> Again, just how does one do that?
> 


Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).