So you can use the mount option "minorversion=1", like
mount -t nfs4 -o minorversion=1 ...
Continuing my investigations on that topic, it appears that nfs-utils is
build with NFS 4.1 support since at least 1.2.6-3:
https://buildd.debian.org/status/fetch.php?pkg=nfs-utils&arch=amd64&ver=1%3A1.2.6-3&stamp=1341956993
dpkg-buildpackage: source package nfs-utils
[...]
CFLAGS="-g -Wall -O2" ./configure \
--mandir='${prefix}/share/man' \
--enable-nfsv41 \
--enable-ipv6 \
--enable-libmount-mount \
--with-tcp-wrappers
... so are the Debian kernels for Jessie and Wheezy:
sylvain@bural:~$ cat /boot/config-3.2.0-4-amd64 | grep _NFS_V
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_V4_1=y
sylvain@bural:~$ cat /boot/config-3.9-1-amd64 | grep _NFS_V
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=m
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
But strangely /proc/fs/nfsd/versions seems to disagree with that (both
on client and server):
root@real:~# cat /proc/fs/nfsd/versions
+2 +3 +4 -4.1
More (?) strangely, /var/log/syslog shows some sign of NFS 4.1 support:
Jul 10 16:05:54 real kernel: [ 11.126765] RPC: Registered tcp NFSv4.1
backchannel transport module.
At this point, I'm quite puzzled. I have the strange feeling that
NFSv4.1 + Krb5 should work -- but somehow don't on our network ?!?
Either there is really a bug somewhere - or there is some kind of oddity
on our machines' configuration.
Could someone confirm successful deployment of NFSv4.1 + Krb5 on Debian
Wheezy -- so I would stop chasing ghost bugs (and stop bothering you at
the same time).
-- Sylvain
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
