On 12/17/14 22:22, J. Bruce Fields wrote: > On Tue, Dec 16, 2014 at 10:19:18PM +0000, Holger Hoffstätte wrote: >> (..oddly broken directory over NFS..) > That doesn't sound familiar. A network trace showing the READDIR would > be really useful. Since this is so reproducible, I think that should be > possible. So do something like: > > move the problem file into 3.14/ > tcpdump -s0 -wtmp.pcap -i<relevant interface> > ls the directory on the client. > kill tcpdump > send us tmp.pcap and/or take a look at it with wireshark and see > what the READDIR response looks like.
Thanks for your reply. I forgot to mention that removing other files seems to "fix" the problem, so it does not seem to be spefically the new file itself that is the cause. I captured the "ls 3.14 | head" sequence on both the client and the server, and put the tcpudmp files here: http://hoho.duckdns.org/linux/ - let me know if that helped. Meanwhile I'll try older/plain (unpatched) kernels. So far reverting the client to vanilla 3.18.1 or 3.14.27 has not helped.. Thanks, Holger -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
