Justin Maggard wrote: > On Tue, Aug 11, 2009 at 9:21 PM, Eric Sandeen<sandeen@xxxxxxxxxx> wrote: >>> - 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. > > Thanks for looking into this. That log message is from when I was > running a 32-bit kernel, oh! ok I missed that tidbit. Although even full 32-bit should be able to reach 16T at least. Hmmm > and I was apparently running into page cache > index limitations. That error went away when I switched to a x86_64 > kernel, but there are still other errors, as posted in one of my more > recent messages. Guess I need to catch up a bit. :) -Eric p.s. I ws wrong about the 73G lifetime writes; just mkfsing a 19T filesystem even w/ lazy_itable_init=1, it did 351G of writes at mkfs time so that's not it. > -Justin -- 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
