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

Michael Biebl biebl at debian.org
Fri Sep 9 22:44:20 BST 2016

Thanks for the hint, Michal.

Seems like someone else already came to the same conclusion:

Am 07.09.2016 um 18:31 schrieb Michal Schmidt:
> 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.

That sounds interesting. Can you give some more details how to use and
setup dm-delay? I have a possible fix in mind and would like to test
that with dm-delay.

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160909/152d5ef0/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list