Am 15.11.2015 um 09:51 schrieb Manuel Bilderbeek: > Package: systemd > Version: 227-3 > Followup-For: Bug #788050 > > Dear Maintainer, > > I'm also hit by this bug. Especially in combination with #804910 (see there), > this is really annoying. > > I saw some workaround and suggestions, but is there already a direction of a > solution of this issue?
I'm afraid not. Not being able to reproduce this issue (on my side) makes this harder. > On my system, fsck'ing the 500GB HDD takes about 20 minutes. It's now aborted > after 9 and a half minutes, see #804910. > > IMHO, you can't sensibly define a timeout for an fsck. I think it's better to > just 'trust' on it to be completed at some point (either with error or > success), because introducing a timeout seems to cause more issues than > relying > on an exit. You can't ever guess what the timeout value should be. Who knows > what kinds of partitions people use... > > So, can you please change the package such that the timeouts of fsck's are > disabled by default? I think the timeout in systemd-fsckd was a red herring. For some other reason systemd-fsckd seems to kill the running fsck process and we haven't figured out yet when and why. Can you reproduce the issue reliably? I tried it with an external USB 3TB hard drive, in a VM with a huge interna ext3 disk. In both cases the fsck process took longer then the default 3min default timeout and completed successfully. So I guess we haven't found the real culprit yet. -- 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
