On Feb 15, 2013, at 7:00 AM, Tuomas Räsänen <tuomasjjrasanen@xxxxxxxxxx> wrote: > ----- Original Message ----- >> From: "Chuck Lever" <chuck.lever@xxxxxxxxxx> >> >> Have you tried a kernel at commit 05f4c350 but with the compilation fix >> applied, then one with 05f4c350 removed, to confirm that this indeed is the >> commit that introduces the problem? > > Yes. With commit 05f4c350 + the compilation fix, the problem occurs, but without > 05f4c350, the parent (6f2ea7f) works as expected, requesting for service <null>. > >> >> When the mount operation fails, is it the first time this client attempts to >> mount a share on server.example.org, or does the client already have mounts >> of server.example.org, possibly using other security flavors? > > Yes, the problem occurs on the very first mount attempt. Thanks for confirming. Did you try updating nfs-utils on your NFS client to 1.2.8-rc1 or later (specifically to replace rpc.gssd)? -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
