Thanks for the hint, Michal. Seems like someone else already came to the same conclusion: https://gist.github.com/ebautistabar/82811d492231700ab2471dd9048502b7
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?
signature.asc
Description: OpenPGP digital signature
