In practice, you need to be quite an expert to do anything other than -y, and
even then you will probably only do so if the disk has data on it that you
cannot recover any other way.
for just about any production situation, you would want to build a new system or
restore from replica/backup instead of doing a manual fsck, but that assumes
that you _have_ the backup and can correctly recreate the server, which should
be the case, but sometimes isn't ;-p
David Lang
On Thu, 3 Oct 2013, Kevin Sandy wrote:
We recently had some issues with one of our filers that wreaked all kinds
of havoc on our systems. Many had to be rebooted to recover from read-only
root filesystems, and quite a few of those needed a manual fsck. Which led
me to wonder:
When faced with filesystem inconsistencies at boot, does anyone do anything
other than just 'fsck -y' on the device? I've never known anyone to do
anything else, but I would have to assume some do, otherwise wouldn't it be
automatic?
-- kevin
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
