[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110727204724.GA21314@infradead.org>
Date: Wed, 27 Jul 2011 16:47:24 -0400
From: Christoph Hellwig <hch@...radead.org>
To: R?diger Meier <sweet_f_a@....de>
Cc: Christoph Hellwig <hch@...radead.org>,
Bryan Schumaker <bjschuma@...app.com>,
Justin Piszcz <jpiszcz@...idpixels.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
xfs@....sgi.com
Subject: Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop
On Wed, Jul 27, 2011 at 10:26:55PM +0200, R?diger Meier wrote:
> At the time I've started this thread
> http://comments.gmane.org/gmane.linux.nfs/40863
> I had the feeling that the readdir cache changings in 2.6.37 have
> something to do with these loop problems.
>
> After that thread I've accepted that's a general problem with
> ext4/dirindex and nfs but seeing it again on xfs with just 5000 files
> I'm in doubt again.
Two separate issues. For one thing the nfs code simply doesn't seem
to handle changing directories very well, and one and a half the Linux
NFS server might even send incoherent readdir output in a single
protocol reply.
Issue two is that the ext3/4 hashed directory format is too simply (not
to say dumb) to provide a proper 32-bit linear value for the dirent
d_off field. It's not a complex task, and the first relatively simple
generation of xfs btree directories couldn't handle it either. The
v2 directory format handles it fine, but at the cost of a much more
complex codebase.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists