linux-ext4 - Re: Problem with 15TB logical volume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C63FA81.8060306@redhat.com>
Date:	Thu, 12 Aug 2010 09:43:29 -0400
From:	Eric Sandeen <sandeen@...hat.com>
To:	Adam Huffman <bloch@...durin.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Problem with 15TB logical volume

Adam Huffman wrote:
> Hope it's okay to send "user problems" here.  

Sure, that's fine.

> I've made a 15TB logical volume on a 21TB RAID6 iSCSI array.
> 
> When I try to make an ext4 filesystem I see the following error:
> 
> mke4fs -E stride=32 stripe-width=384 -i 65536 -j -v \
> /dev/mapper/vg2md3000isata-homes2 
> 
> mke4fs 1.41.9 (22-Aug-2009)
> mke4fs: invalid blocks count - /dev/mapper/vg2md3000isata-homes2


You're not specifying the -E options correctly:

[root@...t e2fsprogs]# misc/mke2fs.static -t ext4 -E stride=32 stripe-width=384 /mnt/test2/testdir/bigfile 
mke2fs 1.41.12 (17-May-2010)
mke2fs.static: invalid blocks count - /mnt/test2/testdir/bigfile

This works - you need comma-separated -E options:

[root@...t e2fsprogs]# mke4fs -E stride=32,stripe-width=384 /mnt/test2/testdir/bigfile 
mke4fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=32 blocks, Stripe width=384 blocks
1006632960 inodes, 4026531840 blocks
...

Without the comma, mkfs thinks you are trying to mkfs a device called
"stripe-width=384" with a block count of "<devicename>"

Odd eh ;)

Perhaps echoing back the blocks count which it found to be invalid
(in this case the devicename string) would make the failure more
obvious...


> When i searched briefly yesterday, some documentation stated that the
> filesystem limit was now 16TB, and some that the limit was much higher.

Yep that should work.

-Eric
 
> The system is running Centos 5.5, e4fsprogs-1.41.9-3.el5.


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html