On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
> 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
mount.nfs4 prints this not very enlightening message if the mount
syscall fails with EINVAL.
> Maybe systemd uses an own impementation of mount.nfs4 and that doesn't
> support the 'sec=krb5i' option?
No, it uses the tools from nfs-common.
> Executing the exact ExecMount command
> line from above manually after the boot process works as expected.
Maybe rpcbind was started too late, see bug #763315[1] on that topic.
What is the output of "systemctl status rpcbind.service"?
Cheers,
Sven
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763315
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/878ub6v0oq....@turtle.gmx.de
