|
With maildir using one file per email, it tends to eat up inodes really fast. ReiserFS doesn't have as much of a problem with that as ext2/3 does. It does still have it though with a limit on the number of files you can have in one directory. I've hit the limit myself before, but it's much higher than with the default inode ratio the LPM sets (and you could in fact just format a ext2/3 partition for yourself using a custom higher inode ratio that should work fine so you don't run out of inodes). ReiserFS has shown it does work a lot faster in benchmarks with tons of smaller files like your going to get with maildir. I can confirm that rumor, but it's unlikely that you'll notice the difference.
May I suggest one thing though... If you want to move to ReiserFS, format a partition that only holds your mail directories, and keep backups like you should be in the first place. ReiserFS seems to have a lot of disappointed users from broken filesystems (I've heard a lot of comments about fsck.reiser making people's partitions un-recoverable).
I thought I would give all the warnings first, but I am a fan of ReiserFS, and have not run into a single problem in the 3-4 years I've been using it. I've even written a GUI frontend to a reiserfs library for reading ReiserFS partitions under Windows some time ago that I still use to this day. Then again, ext3 has never failed me either, I just like to think towards the future of Reiser4, and the million of possibilities it opens up as a filesystem.
|