Am 08.06.2015 um 10:26 schrieb Michael Biebl: > Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue: > >> For a few days now each time the computer boots it forces a file system >> check on two of my disks. >> >> Here is the relevant journalctl entry : >> >> Jun 08 07:48:19 leonardo kernel: input: PS/2 Generic Mouse >> as /devices/platform/i8042/serio1/input/input8 >> Jun 08 07:50:50 leonardo systemd-fsck[459]: fsck: Warning... fsck.ext4 >> for device /dev/sdb1 exited with signal 13. >> Jun 08 07:50:50 leonardo systemd-fsck[459]: fsck failed with error code >> 8.
[..] > Afaics, the underlying problem is, that fsck fails to fix the problems. > So it's rerun on each boot. > > What odd though, return code 13 is the sum of > > 1 Filesystem errors corrected > 4 Filesystem errors left uncorrected > 8 Operational error > > So, fsck at the same time says the errors were corrected, on the other > side it says they weren't. > Am I interpreting the return codes correctly? > > CCed the e2fsprogs maintainers for input. Sorry, somehow I completely overlooked the "signal" string. So signal 13 means SIGPIPE, pitti suspects a communication error between fsck -C <-> systemd-fsck and the actual return code is 8, i.e. Operational error. He also points out, that systemd ignores any return codes from fsck other then 2 and 6. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
