[systemd-devel] systemd-growfs blocks boot until completed

Uoti Urpala uoti.urpala at pp1.inet.fi
Sat Sep 28 11:40:28 UTC 2019


On Fri, 2019-09-27 at 17:12 +0200, Mirza Krak wrote:
> This is what the systemd-growfs at .service looks like:
> 
> # Automatically generated by systemd-fstab-generator
> [Unit]
> Description=Grow File System on %f
> Documentation=man:systemd-growfs at .service(8)
> DefaultDependencies=no
> BindsTo=%i.mount
> Conflicts=shutdown.target
> After=%i.mount
> Before=shutdown.target local-fs.target
> 
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/lib/systemd/systemd-growfs /data
> TimeoutSec=0

The "Before=local-fs.target" means that local filesystems will not be
considered mounted before the oneshot unit has completed. Lots of other
stuff in boot will depend on local filesystems being mounted, so this
will effectively block boot. I don't think this has changed between
systemd versions - the first growfs version seems to have a similar
line. All generated growfs units have such a dependency; the only thing
that could change is the target, it could be "remote-fs.target" if the
filesystem is considered a remote one.




More information about the systemd-devel mailing list