3 ms·
Sure. With huge storage arrays, fsck might take a long time. systemd by defaults aborts after some time and will not mount that array.
by telmich 9y ago
Sure. With huge storage arrays, fsck might take a long time. systemd by defaults aborts after some time and will not mount that array.
- jamiesonbecker 9y agoSo your file system check is killed and leaves your array in a possibly corrupt state? That is simply insane.
- majewsky 9y agoDid you file that in the systemd issue tracker? I had a quick look and couldn't see a report there: https://github.com/systemd/systemd/issues?utf8=%E2%9C%93&q=is%3Aissue+fsck+timeout https://github.com/systemd/systemd/issues?utf8=%E2%9C%93&q=i... This could be an honest mistake. On my system, systemd-fsck-root.service and systemd-fsck@.service have `TimeoutSec = 0`, which I guess to mean "no timeout", but the systemd-fsck executable could have its own timeout. In any case, filing a bugreport sounds much easier than switching distributions.