On Wed, Oct 31, 2012 at 8:33 AM, Sven Geggus <lists@xxxxxxxxxxxxxxxxxxxxx> wrote: >> In case you missed my previous message, "I use debian testing here and >> NFSv4. My clients are running kernel 3.6.3, server is running 3.6.2. No >> problems here". > > No, I did not miss your post. I even asked if you are using sec=krb5. I did > not try if it works without using kerberos, because I am not interested in > "No File Security" NFS3-like mode. Ahh sorry. I misread your post and thought it was directed towards someone else. No, I'm not using sec=krb5. >> It would seem you only need to cherry-pick server changes between 3.6.2 >> and 3.6.3...? > > Unfortunately not. It already did not work using 3.6.2 You could always write a simple script to download & compile each kernel inbetween that range, then just boot into each and find where the breakage occured that way. Sometimes its easier than sifting through a sea of changes. :) -- 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
