Hey Carl- On Oct 28, 2014, at 6:12 AM, Carl Hetherington <cth@xxxxxxxxx> wrote: > Hi Chuck, > > [snip] > >> After the test has been running for ten minutes, the id_resolv >> keys expire, and id_legacy keys appear. Before the above commit, >> the id_resolv keys would simply be refreshed and operation >> would continue normally. > > This sounds a lot like a bug I have seen, our investigations into which > are summarised here: > > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1124250 Looks like a lot of folks are having trouble, and there are two or three sets of independent symptoms reported in the comments. Thanks for bringing it to this forum. I might have a different issue from the bug report, though: + 1124250 might be a server-side problem, and my problem is definitely on the NFS client + My system works fine with kernels up to 3.12 + I can reproduce with just one user, so probably not a key quota issue + I’ve got keyutils installed already > There's an inexpertly written (by me) patch in that bug report (which I > posted to this list recently, too) which (in a nutshell) makes the > idmapper code call up to userspace to get a new key when the current ones > have expired. David should have a look at this. However, your patch changes the behavior of renewing legacy ID resolver keys AFAICT? On my system, at least, we shouldn’t even be getting this far. I’ll poke around more. -- 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
