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

Michael Biebl biebl at debian.org
Wed Sep 14 23:18:46 BST 2016

Control: tags -1 + pending

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.
> The bug is specific to Debian/Ubuntu, because systemd-fsckd is not
> present in upstream.

Thanks again for your input, Michal.

I've committed a fix to our git repository.
It should be included in the next upload.
If someone want's to test the fix earlier, the commit is available at [1].



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://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160915/dedd1e80/attachment.sig>

More information about the Pkg-systemd-maintainers mailing list