On Tue, 2011-01-25 at 15:29 -0800, Nathan March wrote: > On 1/25/2011 2:28 PM, Trond Myklebust wrote: > > On Tue, 2011-01-25 at 14: > > Does '-e' in perl only do a lookup, or does it result in a 'stat()' > > call? If the latter, then your test is flawed: a stat() is a lookup+a > > getattr, and the latter can definitely return ESTALE when you are > > constantly replacing the file. > > > > Cheers > > Trond > > Hi Trond, > > Has any behavior here changed between 2.6.19 and 2.6.32 that you know of? > > Testing that perl one liner out with a variety of nfs setups we run: > > 2.6.11 client vs 2.6.32 server - no error > 2.6.11 client vs netapp - no error > 2.6.19 client vs 2.6.19 server - no error > 2.6.19 client vs netapp - no error > 2.6.32 client vs 2.6.32 server - stale file handles > 2.6.32 client vs netapp - stale file handles > > So it seems to be a client specific change sometime between 2.6.19 and > 2.6.32.... You are probably seeing an effect due to attribute caching. Newer kernels have tighter restrictions on when they are allowed to cache. IOW: I suspect the above is just a timing artefact that would probably disappear on a slower machine. Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.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