I have been, it seems wrongly, assuming that if xfs_check finds
a problem on the disk that the exit code is non-zero. (And,
conversely, if all is well, that the exit code is zero)
Anyway, I have, this weekend, had some problems with one of my machines.
(I have not fully diagnosed the problem so I don't want to point fingers
at XFS yet). During the recovery process, I used my /boot recovery
script and, while xfs_check found errors, the exit code of xfs_check
was zero. This prevented auto-recovery from working.
Is the exit code part of the defined API for xfs_check? Could it be
part of the defined behavior?
For now I will need to check if xfs_check has any output - which is
almost as good as long as that behavior is "defined"
--
Michael Sinz -- Director, Systems Engineering -- Worldgate Communications
A master's secrets are only as good as
the master's ability to explain them to others.
|