Leonard den Ottolander (leonard(a)den.ottolander.nl) said:
I suspect this might have to do with the fsck return codes being
wrongly
interpreted. Any value larger than 1 is considered a failure by the
script.
With an fsck result code of 3 however the system passes the next fsck
with no errors whatsoever. Could it be that fsck's result code on
failure actually is -1? Or any other value? Or does initlog (via which
fsck is called) somehow change the result value?
It shouldn't change it, no.
Bill