After looking through various patches that were posted to LKML, I
discovered that passing "-F" to mke2fs seems to make this work as
expected.  However, this behavior seems to be undocumented and that
makes me more then a little nervous.

The resulting filesystem does seem to be mountable:

    /dev/sda4               11T   173M    11T   1% /export/ipp003.0

Is this feature undocumented for a reason or is it just unsupported?

-J

--
On Mon, Apr 09, 2007 at 02:12:43PM -1000, Joshua Hoblitt wrote:
> Ps.  I've looked through e2fsprogs configure.in and it doesn't look like
> there's a magic flag to enable this support either.
> 
> -J
> 
> --
> On Mon, Apr 09, 2007 at 02:09:10PM -1000, Joshua Hoblitt wrote:
> > After reading in the kernel changelog that 2.6.19 should support ext3
> > filesystems up to 16TB in size, I tried to create an 11TB filesystem.
> > Attempting to do so gets this error from mke2fs:
> > 
> > # mke2fs -j -J size=400 -O sparse_super,dir_index -i32768 -m1 /dev/sda4 
> > mke2fs 1.39 (29-May-2006)
> > mke2fs: Filesystem too large.  No more than 2**31-1 blocks
> >          (8TB using a blocksize of 4k) are currently supported.
> > # mke2fs -j /dev/sda4
> > mke2fs 1.39 (29-May-2006)
> > mke2fs: Filesystem too large.  No more than 2**31-1 blocks
> >          (8TB using a blocksize of 4k) are currently supported.
> > 
> > This is on a system running 2.6.19-gentoo-r5 with sys-fs/e2fsprogs-1.39
> > 
> > ChangeLog for in kernel 16TB ext3 support:
> > 
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=855565e81ad8940cc645b5110ec2c7f124a76d23
> > 
> > Release notes for e2fsprogs claiming 16TB support (2**32 blocks).
> > 
> > http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.39
> > 
> > Any idea what I am missing?
> > 
> > Cheers,
> > 
> > -J
> > 
> > --
> 
>