Well, there was a tail merging patch for ext2, but it has been dropped
for now. In reality, any benchmarks with reiserfs (except the
very-small-files case) will run with tail packing disabled because it
kills performance.
> - B*Tree allocation offering ``a 1/3rd reduction in internal
> fragmentation in return for slightly more complicated insertions and
> deletion algorithms'' (from the htree paper).
> - online resizing in the main kernel (ext2 needs a patch -
> http://ext2resize.sourceforge.net/).
Yes, I wrote it...
> - Resizing does not require the use of `ext2prepare' run on the
> filesystem while unmounted to resize over arbitrary boundaries.
That is coming this summer. It will be part of some changes to support
"meta blockgroups", and the resizing comes for free at the same time.
> - directory hashing in the main kernel
Probably will happen in 2.5, as Andrew is already testing htree support
for ext3. It is also in the ext3 CVS tree for 2.4, so I wouldn't be
surprised if it shows up in 2.4 also.
> On the flipside, ext2 over reiserfs:
>
> - support for attributes without a patch or 2.4.19-pre4+ kernel
> - support for filesystem quotas without a patch
> - there is a `dump' command (but it's useless, because it hangs when you
> run it on mounted filesystems - come on, who REALLY unmounts their
> filesystems for a nightly dump? You need a 3 way mirror to do it
> while guaranteeing filesystem availability...)
Well, the dump can only be inconsistent for files that are being changed
during the dump itself. As for hanging the system, that would be a bug
regardless of whether it was dump or "dd" reading from the block device.
A bug related to this was fixed, probably in 2.4.19-preX somewhere.
> I'd be very interested in seeing postmark results without the
> hierarchical directory structure (which an unpatched postfix doesn't
> support), with about 5000 mailboxes with and without the htree patch
> (or with the htree patch but without that directory indexed, if that
> is possible).
Let me know what you find. It is possible to use an htree-patched
kernel and not have indexed directories - just don't mount with
"-o index". Note that there is a data-corrupting bug somewhere in
the ext3 htree code, so I wouldn't suggest using indexed directories
except for test.
Cheers, Andreas
-- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/