Apparently, the size the filesystem is a factor, too. I doubled the size of the filesystem to 2 GB and I had to double the number of files to get the error. I would have expected the limit on the directory size to remain constant.
+ ls -U + wc -l 900545 + date Wed May 26 19:48:00 EDT 2010 + grep warn /var/log/kern.log + tail -2 May 26 19:47:59 mnx-lucid kernel: [1412301.524937] EXT3-fs warning (device loop0): ext3_dx_add_entry: Directory index full! May 26 19:47:59 mnx-lucid kernel: [1412301.525175] EXT3-fs warning (device loop0): ext3_dx_add_entry: Directory index full! + df -i . Filesystem Inodes IUsed IFree IUse% Mounted on /dev/loop0 1024000 900557 123443 88% /tmp/test/loop + df -h . Filesystem Size Used Avail Use% Mounted on /dev/loop0 1.8G 51M 1.6G 4% /tmp/test/loop Interesting, although, expanding the filesystem is not an option for us, either. Regards, - Robert On Wed, May 26, 2010 at 6:55 PM, Robert Citek <[email protected]> wrote: > Yes, a solution is to have larger block sizes. > > On Wed, May 26, 2010 at 4:59 PM, David Dooling > <[email protected]> wrote: >> On Wed, May 26, 2010 at 03:42:01PM -0500, Mike B. wrote: >>> gotcha. I wonder if the file system itself is corrupt? >> >> Looks like it is just a limit of ext3. >> >> http://kerneltrap.org/mailarchive/linux-kernel/2008/5/18/1861684 >> >> Looks like the workaround is to use a bigger block size. -- Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug
