Hi, [...]
systemd tries to mount the second fstab entry before the network and name resolution are available, while the first one is mounted correctly after the network is available and named has been started. And yes, the entries are shown in that order in the journal, though the time seems to jump back and forth.
I can't see any difference between the two entries. Why does systemd treat them different?
systemctl show upnp\x2droot\x2dremote-VDR_Videos.mount var-spool-video-video0.mount would be good start.
they differ in a few entries: ------------------------< snip snip snip >----------------------------- [...] < Result=exit-code ---
Result=success [...] < After=network.target remote-fs-pre.target -.mount systemd-journald.socket system.slice network-online.target < RequiresMountsFor=/upnp-root-remote
After=system.slice network-online.target systemd-journald.socket remote-fs-pre.target -.mount nfs-server.service network.target RequiresMountsFor=/var/spool/video [...] < NeedDaemonReload=yes
NeedDaemonReload=no [...] ------------------------< snip snip snip >-----------------------------
The difference for After= can explain the different behaviour on boot. But both entries are created by systemd-fstab-generator. So the question keeps the same: Why is systemd treating both entries different? Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org