2tb limit?

[Dan Lund]

Well, here's the whole setup:

An AMD64 Opteron 246 w/2 gb ram, with 2 IDE "system" disks installed.
I raid1 them through software raid.

I have 16 SATA disks attached via an Areca SATA RAID card which is
configured with a RAID6+2 failover setup.
I use LVM2 to split them up amongst their different partitions, and I
have 3.2TB allocated to this particular partition.

After looking at the raw /dev/sda disk (allocated by the Areca driver,
and setup as a physical device in my volume group) it is labelled
msdos.  Would that cause a problem being so low in the layers?

If I change it, how would I make it accessible again via parted?  I'm
not terribly versed in parted.  Just looking at the params, my guess
would be to run mklabel, and once the partition table is killed, run
rescue with a start and end.. but where to get those numbers?

Either way, I'm dumping the whole partition to tape tonight.



On 5/2/07, steve crandell <steven.crandell at icrossing.com> wrote:
> Take a gander at your disk label.
> # parted /dev/sdx
>  > print
>
> I'm guessing it will be msdos.
> If so, that's your problem.
> Consider using gpt instead.
>
> Note: changing a disk label will render your data unusable, though it
> will technically be `rescue`-able using gnu parted.
>
> That said I'd consider copying it off-disk prior to making any changes
> if possible.
>
> Dan Lund wrote:
> > Well I doubt its failing hardware on a raid6+2, I was leaning more
> > towards device constraints and was wondering if anyone else has dealt
> > with a device greater than 2tb.
> >

-- 
"Courage is like love; it must have hope to nourish it."
-Napoleon Bonaparte