Bug#788050: systemd-fsck : Check disks at each reboot
mschmidt at redhat.com
Wed Sep 7 17:31:12 BST 2016
systemd-fsckd's event loop terminates if nothing happens for 30 seconds
(IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
than that, but the interval is not guaranteed. So systemd-fsckd may exit
by itself while fsck is busy working. When this happens, fsck will
receive SIGPIPE as soon as it tries to write the next progress update.
It is possible to reproduce this using the dm-delay DM target for
a block device.
The bug is specific to Debian/Ubuntu, because systemd-fsckd is not
present in upstream.
More information about the Pkg-systemd-maintainers