Re: auto-mount NFS shares on boot
Hi again,
Am 2015-06-26 18:15, schrieb Sven Joachim:
On 2015-06-26 17:42 +0200, Jonas Meurer wrote:
While searching the web I learned that Ubuntu and Redhat based distros
seem to support the '_netdev' option to entries in /etc/fstab for such
cases, but it seems like Debian doesn't support this option, right?
Huh, what makes you think so? The option is mentioned in mount(8) and
has been present since util-linux version 2.11x, released 2002.
Oops, I searched only in fstab(5) and nfs(5) manpages. Still, the
option doesn't work:
# grep nfs /etc/fstab
nfs-server:/vmail /var/vmail nfs4 _netdev,sec=krb5i,bg 0 0
results in unmounted NFS shares after reboot and:
[FAILED] Failed to mount /var/vmail.
See 'systemctl status var-vmail.mount' for details.
[DEPEND] Dependency failed for Remote File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting LSB: Prepare console...
# 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
Jun 26 16:29:02 clt systemd[1]: var-vmail.mount mount process exited,
code=exited status=32
Jun 26 16:29:02 clt systemd[1]: Failed to mount /var/vmail.
Jun 26 16:29:02 clt systemd[1]: Unit var-vmail.mount entered failed
state.
Am 2015-06-26 18:01, schrieb Michael Beck:
does the NFS-"soft"-mount-option work for your NFS-Client?
nope, doesn't help either.
Actually, even with only 'sec=krb5i' as single option, 'systemctl
status var-vmail.mount' reports afterwards:
[...]
Process: 351 ExecMount=/bin/mount -n nfs-server:/vmail /var/vmail -t
nfs4 -o sec=krb5i (code=exited, status=32)
Jun 26 16:34:08 clt mount[351]: mount.nfs4: an incorrect mount option
was specified
Jun 26 16:34:08 clt systemd[1]: var-vmail.mount mount process exited,
code=exited status=32
Jun 26 16:34:08 clt systemd[1]: Failed to mount /var/vmail.
Jun 26 16:34:08 clt systemd[1]: Unit var-vmail.mount entered failed
state.
Maybe systemd uses an own impementation of mount.nfs4 and that doesn't
support the 'sec=krb5i' option? Executing the exact ExecMount command
line from above manually after the boot process works as expected.
Cheers,
jonas
Reply to: