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

[Michael Biebl]

Might have been a red herring 

Am 28. November 2015 15:36:12 MEZ, schrieb Martin Pitt <mpitt at debian.org>:
>Hey Michael,
>
>Michael Biebl [2015-09-24 18:32 +0200]:
>> Am 24.09.2015 um 17:46 schrieb hannu.tmp at pp.inet.fi:
>> > This works for me:
>> > 
>> > copy /lib/systemd/system/systemd-fsckd.service to
>/etc/systemd/system
>> > 
>> > edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec
>under [Service]
>> > 
>> > [Service]
>> > TimeoutStartSec=60min
>> 
>> Hm, good point. We should probably disable the Timeout completely
>like
>> in systemd-fsck-root.service and systemd-fsck at .service by setting
>> 
>> TimeoutStartSec=0
>> 
>> The default is 90s, and an fsck for a large disk can certainly take
>> longer for ext3.
>
>Do you happen to know *why* this works? fsckd.service is not a
>Type=oneshot, and I don't see why the actual startup of the process
>should take that long?
>
>Martin
>-- 
>Martin Pitt                        | http://www.piware.de
>Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Pkg-systemd-maintainers mailing list
>Pkg-systemd-maintainers at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151128/e81f7946/attachment-0002.html>