AW: Problem with more than 1T B

[Andreas Dilger]

On Dec 08, 2004  18:10 +0100, Christian wrote:
> Tobias Amon schrieb:
> >I use e2fsprogs version 1.5.2 (I think)
> 
> http://e2fsprogs.sourceforge.net/  exists, latest version is 1.35.
> 
> >I got another solution. Yast, which came with Suse
> >is not able to create partitions larger than 2 TB
> >the "parted" tool can do so.

So this is entirely a problem with Yast, and not mke2fs/e2fsprogs.
Please ask SuSE about that.

When you do create such a large filesystem, it would be sensible to test
it once first by creating some large files in the fs (enough to fill it
up, either many small ones or fewer large ones) that have a verifiable
data pattern in them, like "64-bit byte_offset:32-bit inum" at the start
of each 4kB block.  Then read back the files and verify the data is still
correct.  If this fails, try the same thing on the raw block device to
check if it can write data > 2TB at the correct offsets.

The reason I ask is that I'm personally not 100% convinced that larger
than 2TB filesystems are working properly yet.  One of our customers was
testing with a ~4TB filesystem and they experienced data corruption when
writing > 2TB of data.  Since it was only for a demo we just went with
mutliple 2TB filesystems and have not had an opportunity to determine
if the problem was in MD RAID or ext3.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/             http://members.shaw.ca/golinux/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20041208/6b714b55/attachment.sig>