> From: svenj...@gmx.de > Date: Fri, 26 Jun 2015 19:28:37 +0200 > > On 2015-06-26 18:38 +0200, Jonas Meurer wrote: >>> >>> # systemctl status var-vmail.mount >>> ● var-vmail.mount - /var/vmail >>> Loaded: loaded (/etc/fstab) >>> Active: failed (Result: exit-code) since Fri 2015-06-26 16:29:02 >>> UTC; 6s ago >>> Where: /var/vmail >>> What: nfs-server:/vmail >>> Docs: man:fstab(5) >>> man:systemd-fstab-generator(8) >>> Process: 352 ExecMount=/bin/mount -n nfs-server:/vmail /var/vmail >>> -t >>> nfs4 -o sec=krb5i,_netdev (code=exited, status=32) >>> >>> Jun 26 16:29:02 clt mount[352]: mount.nfs4: an incorrect mount >>> option was specified > > mount.nfs4 prints this not very enlightening message if the mount > syscall fails with EINVAL.
If I've understood the mount scripts correctly, the error is correct: the _netdev mount option is for mount scripts only, and should /not/ be passed to the mount command. I would guess that this is another case where systemd breaks backwards compatibility. Maybe it's mentioned in the release notes? Regards, Arno