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

[gaf at blu.org (Jerry Feldman)]

Normally, the fsck at boot time (actually single to multi-user transition on 
most Unix systems) should suffice. If I suspect a problem with a file 
system, or when I get the inconsistency message, I then use fsck -fsy 
<file system>

-f - force
-s - serial (not parallel - not necessary when chcking a single file system).
-y - answer yes. 

I think it might be gangerous to use the -y parameter during boot. You 
might find that under some circumstances it could really screw up a file 
system.
On 2 Feb 2001, at 9:35, Glenn Burkhardt wrote:

> This question really applies to all Unix systems (I think - at least, it 
> applies to SunOS, Solaris, and Linux).
> 
> Occasionally after a power failure, the disk check after boot will fail, 
> dropping the system into single user mode.  The way I've always dealt with it
> is to execute 'fsck -y /dev/<devname>' after the single user command prompt
> comes up.
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).