Justin Maggard wrote: > I've been toying with ext4 and e2fsprogs pu branch (pulled from git > yesterday) on very large volumes, and I've run into some issues. What > I've found so far with an 19TB MD RAID0 volume, running 2.6.29.4 (I'm > planning on trying 2.6.30 soon): > > - mkfs.ext4 *appears* to work fine, reporting no errors. Examining > the superblock info with dumpe2fs -h looks normal -- although I'm > unfamiliar with "Lifetime writes" field, and I'm not sure why it's at > 73GB immediately after doing mkfs, before ever mount it. Guessing that's how much metadata actually gets written during mkfs. > - Immediately running e2fsck on the volume before ever mounting it > will not complete, and results in the following: > # e2fsck -n /dev/md2 > e2fsck 1.41.7 (29-June-2009) > Error reading block 2435874816 (Attempt to read block from filesystem > resulted in short read). Ignore error? no This is roughly halfway through the filesystem; the journal is roughly in the middle of the filesystem; this is just over 2^31 blocks. I bet there are still ints or longs in the userspace journal code. I'll take a look. -Eric -- 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
