Lately, I had a serious performance problem on a 1.2 TB ext3 filesystem
placed on LVM, which was placed on Linux RAID-5.
Luckily, it was possible to alleviate much of this problem by removing
internal bitmap from RAID-5 and by using anticipatory IO scheduler.
As suggested earlier by Theodore Tso in "very poor ext3 write
performance on big filesystems" thread on linux-fsdevel list, I should
have used "mke2fs -E stride option to make sure all of the bitmaps
don't get concentrated on one hard drive spindle".
Although the fine mkfs.ext3 manual gives some basic information on how
to do it if you place the whole filesystem on a RAID array, it is not
clear to me how it should be done correctly if I want to create a ext3
filesystem on LVM on RAID-5.
Any helpful hints?
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
