[systemd-devel] Why don't remote file systems wait for network-online.target?

Michael Biebl mbiebl at gmail.com
Tue Mar 10 06:18:32 PDT 2015

2015-03-10 12:40 GMT+01:00 Martin Pitt <martin.pitt at ubuntu.com>:
> Hello all,
> we got a report [1] that NFS fstab mounts (sometimes) aren't being
> mounted at boot as the network is still down:
> | mount[866]: mount.nfs: Network is unreachable
> | systemd[1]: mnt-server.mount mount process exited, code=exited status=32
> | systemd[1]: Failed to mount /mnt/server.
> | systemd[1]: Dependency failed for Remote File Systems.
> | systemd[1]: Job remote-fs.target/start failed with result 'dependency'.
> | systemd[1]: Unit mnt-server.mount entered failed state.
> At the moment, neither network-fs-pre.target has no dependencies at
> all, and the fstab-generator-created .mount units only have
> "Before=remote-fs.target" and no other dependencies.
> Wouldn't it make sense to make network-fs-pre.target
> Wants/After=network-online to fix this? If you have/rely on NFS
> mounts, then you usually have some static/always working network
> connection via networkd/auto-connection in NM/ifupdown/etc, which all
> integrate into network-online.target.

Could you share the relevant /etc/fstab line?

Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

More information about the systemd-devel mailing list