On Sat, 2011-05-28 at 17:00 +0200, RÃdiger Meier wrote: > On Saturday 28 May 2011, RÃdiger Meier wrote: > > I could track down the problem to: > > > > commit 0b26a0bf6ff398185546432420bb772bcfdf8d94 > > Author: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx> > > Date: Sat Nov 20 14:26:44 2010 -0500 > > > > NFS: Ensure we return the dirent->d_type when it is known > > > > > > After reverting the problem is gone. > > Actually it's enough to remove d_type from struct nfs_cache_array_entry > again. It's not enough to set it DT_UNKNOWN always. I had to remove it > from struct to let it work. > Tested with kernels 2.6.37.6 and 2.6.39. Sorry, but that patch makes absolutely no sense whatsoever as a fix for the problem you describe. All you are doing is changing the size of the readdir cache entry, which is probably causing a READDIR with a duplicate cookie to trigger. When running with the stock 2.6.39 client, do you see the "directory contains a readdir loop." message in your syslog? 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
