> The stride parameter is the problem. Newer versions of e2fsprogs > don't allow a stride parameter which is too big. If you want to do > the perfect calculation, you take the 64k chunk size, and divide it by > the 4k blocksize to yield a stride parameter of 16. Actually, though, > simply using a non-zero stride size is actually good enough --- and if > you have a even number of RAID-5 disks, you might not need this > parameter at all. (It's only purpose is to perturb the location of > the block bitmaps so that all of the bitmaps don't end up on a single > hard drive.) Actually, as I wrote: >> Removing the stride option didn't help. Removing all options didn't >> help... I still end up with a "blocks per group" of 37265, and when mounted I'm greeted with the message "EXT4-fs: #blocks per group too big: 37265". Is the ext4 code in the 2.6.25-rc8 kernel too old? According to the source the number of block per group must be <= 8 * blocksize; with 4k blocks that would mean 32768, not 37265. Even passing the -g option to explicitly set the blocks per group gets ignored. > BTW, we will be making a new snapshot for people who want to test ext4 > soon.... Kernel code and userspace utils? Or just kernel code? Where can I find the most recent version of both? I looked at Documentation/filesystems/ext4.txt, but I feel that's a bit outdated: - It's still mke2fs -j /dev/hda1 - mount /dev/hda1 /wherever -t ext4dev This ignores the fact you need to set the testing option... Thanks, Paul Slootman -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
