Bug#788050: systemd-fsck : Check disks at each reboot

Paul Menzel pm.debian at googlemail.com
Thu Jul 9 07:46:19 BST 2015


Dear Debian folks,


Am Sonntag, den 05.07.2015, 15:28 +0200 schrieb Paul Menzel:

> Am Montag, den 08.06.2015, 10:48 +0200 schrieb Michael Biebl:
> > 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.
> 
> I am still experiencing this error in Debian Sid/unstable. Could the
> cause be pinpointed? Please tell me, if you need more debug 
> information from an affected system.

Just another observation, that during the fsck run, there is that
systemd time-out message for a unit shown after a while.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150709/198df4a7/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list