nfsv4 + readdir == too many requests
Subsystems (2)
By running intensive tests I notice that readdir oration over nfsv4.1 asks for
file attributes in readdir (attr_request) and later on for each file. To me it looks like
broken.
This 2.6.37 + pnfs-all-latests :
git://linux-nfs.org/~bhalevy/linux-pnfs.git378978453b64bf895de8cd0e68dbcd9e9c0155ce
100% reproducible.
Regards,
Tigran.
Quoted 7 lines · Tigran Mkrtchyan
By running intensive tests I notice that readdir oration over nfsv4.1 asks for
file attributes in readdir (attr_request) and later on for each file. To me it looks like
broken.
Quoted 6 lines
This 2.6.37 + pnfs-all-latests :
git://linux-nfs.org/~bhalevy/linux-pnfs.git378978453b64bf895de8cd0e68dbcd9e9c0155ce100% reproducible.
1) What makes you think this is broken, and not just a case of the attribute cache timing out and/or the directory changing?
2) Can you produce a testcase that proves brokenness?
3) Can you reproduce on a non-pnfs-all-latests kernel?
Readdir shouldn't be affected by the stuff in Benny's tree, but I'm always wary of tests on out-of-mainline trees.
Cheers
Trond
Signature · 6 lines
Trond Myklebust Linux NFS client maintainer NetApp [email protected] www.netapp.com
Quoted 10 lines · Trond Myklebust
Quoted 8 lines · Tigran Mkrtchyan
By running intensive tests I notice that readdir oration over nfsv4.1 asks for
file attributes in readdir (attr_request) and later on for each file. To me it looks like
broken.This 2.6.37 + pnfs-all-latests :
Quoted 8 lines
Quoted 5 lines
git://linux-nfs.org/~bhalevy/linux-pnfs.git378978453b64bf895de8cd0e68dbcd9e9c0155ce100% reproducible.
1) What makes you think this is broken, and not just a case of the attribute cache timing out and/or the directory changing?
The directory does not changed. I issue 'ls -l' and with wireshak can see READDIR requests
followed by GETATTR. looks like cache is ignored or too small.
Quoted 2 lines
2) Can you produce a testcase that proves brokenness?
I will try to come up with something.
Quoted 5 lines
3) Can you reproduce on a non-pnfs-all-latests kernel?
Readdir shouldn't be affected by the stuff in Benny's tree, but I'm always wary of tests on out-of-mainline trees.
NP. with vanilla 2.6.37 ?
Regards,
Tigran.
Quoted 3 lines
Cheers
Trond
Still didn't got a time to test with vanilla kernel. But got some details. It's works as expected with sec=sys. With sec=krb5 I see this effect. Unfortunately kernel crashes as soon as I try to re-run tests. It simply freezes with no stack traces....
Regards,
Tigran
Quoted 41 lines · Tigran Mkrtchyan
Quoted 10 lines · Trond Myklebust
Quoted 8 lines · Tigran Mkrtchyan
By running intensive tests I notice that readdir oration over nfsv4.1 asks for
file attributes in readdir (attr_request) and later on for each file. To me it looks like
broken.This 2.6.37 + pnfs-all-latests :
Quoted 8 lines
Quoted 5 lines
git://linux-nfs.org/~bhalevy/linux-pnfs.git378978453b64bf895de8cd0e68dbcd9e9c0155ce100% reproducible.
1) What makes you think this is broken, and not just a case of the attribute cache timing out and/or the directory changing?
The directory does not changed. I issue 'ls -l' and with wireshak can see READDIR requests
followed by GETATTR. looks like cache is ignored or too small.Quoted 2 lines
2) Can you produce a testcase that proves brokenness?
I will try to come up with something.
Quoted 5 lines
3) Can you reproduce on a non-pnfs-all-latests kernel?
Readdir shouldn't be affected by the stuff in Benny's tree, but I'm always wary of tests on out-of-mainline trees.
NP. with vanilla 2.6.37 ?
Regards,
Tigran.Quoted 3 lines
Cheers
Trond--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html