Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

[Lorenz Hübschle-Schneider]

Well... using a regular mount doesn't work after all, as that results
in an ordering cycle:

Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found ordering
cycle on remote-fs.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on home.mount/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on network-online.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on systemd-networkd-wait-online.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on systemd-networkd.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on dbus.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on sysinit.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on console-setup.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on remote-fs.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Breaking
ordering cycle by deleting job home.mount/start
Nov 20 09:35:48 i10pc82 systemd[1]: home.mount: Job home.mount/start
deleted to break ordering cycle starting with remote-fs.target/start


...maybe that was the reason I was using the automount?

Lorenz

On Thu, Nov 19, 2015 at 4:33 PM, Lorenz Hübschle-Schneider
<lorenz-dev at lgh-alumni.de> wrote:
> Hello,
>
> On Thu, Nov 19, 2015 at 4:07 PM, Michael Biebl <biebl at debian.org> wrote:
>> I just realized, that you use systemd-networkd and
>> systemd-networkd-wait-online. With that setup I do indeed run into a
>> real dead-lock.
>
> Yes, I use systemd-networkd because it's perfectly adequate for my use
> case and I have a (perhaps unfounded) dislike for network manager.
> This is a desktop machine sitting in an office.
>
> I think I activated systemd-networkd-wait-online because otherwise
> LDAP authentication got very confused.
>
> After trying out the options I mentioned earlier, I observed the following:
> - Changing Q/q to v in tmpfiles.d/home.conf fixes the issue completely
> - Using a regular mount instead of an automount for /home fixes the
> issue completely
> - Without any configuration changes, the request does not time out (as
> Michael mentioned above). I waited for 11 minutes, after which I had
> caught up with my twitter stream and aborted the experiment ;)
>
> I ended up using a regular mount for /home now since the automount
> doesn't make any sense any more anyway (it was part of a semi-working
> hack to bind-mount a local dir into the remote mount, which was
> dependent on the right unit being killed when resolving the resulting
> ordering cycle, i.e., the machine booted 9/10 times and I had to
> manually fix mounts the other 10% of the time). Since that's now
> successfully worked around with /etc/rc.local, I don't need the
> automount any more.
>
> Thank you for your help!
>
> Lorenz