On Wed, 2008-08-06 at 10:07 -0400, Theodore Tso wrote: > On Tue, Aug 05, 2008 at 12:53:51PM +0200, Thomas Trauner wrote: > > On Fri, 2008-08-01 at 08:16 -0400, Theodore Tso wrote: > > > On Fri, Aug 01, 2008 at 11:43:40AM +0200, Thomas Trauner wrote: > > > > > > > > I have a problem with directories that contain more than 10000 entries > > > > (Ubuntu 8.04.1) or with more than 70000 entries (RHEL 5.2). If you use > > > > readdir(3) or readdir64(3) you get one entry twice, with same name and > > > > inode. > > > > > > I made new tests with the code under > > <http://www.unet.univie.ac.at/~a9100884/readdir.c> on a bunch of freshly > > generated and empty filesystems, every about 38GB large, of type fat > > (aborted after about 22000 entries because it took to long), ext2, xfs, > > jfs and again ext3.... > > OK, I have a workaroud for you. It appears there's a kernel bug > hiding here, since there shouldn't be duplicates returned by readdir() > even if we have hash collisions. Thank you for your fast help and detailed explanation! Now I've something to read at home ;) Thanks! Tom -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
