On Tue, 2012-08-07 at 16:50 +0200, Joerg Roedel wrote:
> On Tue, Aug 07, 2012 at 10:36:31AM -0400, Bryan Schumaker wrote:
> > Your stack trace is showing v4 calls on the failing box, those
> > definitely shouldn't be happening if you're using v3. Can you double
> > check /etc/fstab and /proc/mounts on a working kernel to be sure?
>
> So the bug is probably (for whatever reason) that the nfs4 path is
> called for an nfs3 mount :)
If your /etc/nfsmount.conf doesn't contain a line of the form
Defaultvers=4
then the mount utility will try NFSv4 by default. That is not a bug, it
is a deliberate feature of recent versions of nfs-utils.
> Anyway, I attach /proc/mounts and /etc/fstab from that box running a
> v3.5-rc5 kernel (where it works).
I'm guessing that the fact you are not running idmapper is causing the
NFSv4 mount to fail on the older kernels, and so the mount program is
falling back to an NFSv3 mount.
We need to fix v3.6 so that it does the same.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
