Parted and very big disks

[amir habibi]

I'm using parted-1.6.22 to partition a 4TB hardware
raid system on a linux system [kernel 2.6.11] and
everything is fine during mklabel/mkpart. Even after
mounting I can use mke2fs to create a ext3 journaled
file system on the raid. 

Unfortunately as soon as I re-run parted on my
/dev/sda, even for printing partition table, that
obviously prints wrong numbers, it writes something
into partition table that leads kernel to read wrong
geometry parameters and I end up with the following
error while mounting that partition:

Attemp to access beyond end of device. 
sda1: rw=0, want=xxxx, limit=xxxx,
EXT3-fs error ext3_get_inode_loc: unable to read inode
block - inode block=xxxxx

Interestingly, when I rm the partition and use rescue
feature to add that entry back to partition table I
can mount the device again and system works perfectly,
but even I run one more parted command I can't
successfully mount the partition.

First Problem is: why should parted modify partition
table when I just ask for printing it.

Second Problem is: why can parted make a very big
partition correctly, but it can't read it back.


Thanks
Amir


                
__________________________________ 
Yahoo! Messenger 
Show us what our next emoticon should look like. Join the fun. 
http://www.advision.webevents.yahoo.com/emoticontest