Re: [BK PATCH] Add ext3 indexed directory (htree) support

[Theodore Ts'o]

On Wed, Sep 25, 2002 at 04:45:34PM -0700, Ryan Cumming wrote:
> I got some pretty nasty results with that patch. After enabling the
> dir_index superblock flag and running e2fsck -fD, the filesystem
> would spontaneously remount itself read-only (I have
> errors=remount-ro set) after a few minutes of use. Once I disabled
> dir_index, e2fsck picked up many duplicate blocks.  There doesn't
> appear to be any severe filesystem damage, however.

Well, I'm currently running with 2.4.19 with the ext3 patch, and I'm
not having any problems.  In fact, my mail directory is an indexed
directory, and I'm replying out of it at this very moment.  I've also
done a number of fairly intensive bitkeeper operations (the
deleted/SCCS directory gets is pretty big for the linux kernel), and
it seems to be working just fine for me.

Are you sure you upgraded to the latest version of e2fsprogs (version
1.29, released yesterday?).  I specified version 1.29 explicitly in my
last e-mail for a reason --- e2fsprogs 1.28 had a bug where e2fsck -fD
had a 1 in 512 chance of corrupting each directory block which it
tries to optimize.  Unfortunately because the fence post error had
only a 1 in 512 chance of triggering, I didn't notice it in my
regression tests.

							- Ted