On 10/30/13 18:38, Brandon Allbery wrote:
Actually, I think -y may be the cause of this? Historically it meant
"fix the utterly trivial stuff and abort and force admin intervention if
anything else is seen, even if it is simple", and it may still have that
meaning for some filesystems. Then again, fsck manpage on Centos6.4
implies the old -n behavior (just check, never fix) no longer exists and
-n is now what -y used to be.
I suggest you verify that -y means what you expect for all the
filesystem types you support.
hhmmm...
In my 20 years "fsck -y" was always "answer yes to all questions."
--
Mr. Flibble
King of the Potato People
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/