10.03.2016 06:01, Anton Aylward пишет:
On 03/09/2016 07:07 PM, Greg Freemyer wrote:
I don't recall using _netdev before, so this could be my config error, but I think I've followed the advice I got.
It's now been 3 hours since I rebooted with these lines in my fstab:
--- 10.200.3.230:/mnt/pacers1/kvm672/kvm672 /srv_new nfs rw,relatime,vers=3 0 0 /srv_new/sftp-container-large /srv/sftp ext4 _netdev,loop 0 0 /srv_new/portal_backup_container /home/portal_backup/portal_backup ext4 _netdev,loop 0 0 ---
The _netdev mounts were only attempted once and that was too soon. Another bug?
The NFS mount happened during the boot process, but seconds BEFORE the 2 mounts with _netdev in the args.
The "_netdev" is for network devices only. It should be on the NFS line and not the "loop" lines. You've got it exactly the wrong way round there.
No, it was exactly correct. _netdev is needed in this case because otherwise systemd does not know that filesystem is related to network and must be attempted after network is configured. For NFS it knows it already so no _netdev is really needed.
The real issue is making the "loop" entries dependent on the NFS.
Normally I expect that it order filesystems automatically. But looking in code, it skips this dependency for network mounts. Not sure why, this is also in current upstream code. It should be possible to force dependencies still.
As you say
Note that the _netdev mount attempts were 5 seconds before that:
That pretty much guarantees it will fail!
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org