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. Michal _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
