<div class="gmail_quote">On Fri, Sep 3, 2010 at 2:33 PM, Jack <span dir="ltr"><<a href="mailto:quiet_celt@yahoo.com">quiet_celt@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
My major issue with -y is that it takes control out of your hands, and if your goal is to attempt to preserve as much as possible, the -y option isn't likely to be helpful there. Remember the original poster wanted to do the least destructive path. Sometimes the right answer is to sit there and press yes 10,000 times (and bill accordingly). After all, fsck already does the best it can to fix the filesystem in the default configuration.<br>
</blockquote><div><br></div><div>Third tier storage support for the following 3 vendors disagree with you: Oracle (Solaris), Hewlett-Packard (HP-UX), SGI (IRIX). I don't know what IBM and Red Hat recommend, I've not supported systems running their products and haven't had to contact them.</div>
<div><br></div><div>The short of it is, if your filesystem is so screwed up that it's not "safe" to do fsck -y, then you need to restore from backup regardless of outcome.</div><div><br></div><div>To the OP,</div>
<div><br></div><div>Run fsck -y on the device repeatedly until it stops complaining (ie; runs without fixing anything). You'll end up being fine.</div></div><div><br></div>-- <br>Chris<br><br><br><br>