From: Christian Schmidt <lkml@digadd.de>
To: linux-kernel@vger.kernel.org
Subject: Help needed: Partitioned software raid > 2TB
Date: Fri, 15 Jun 2007 13:56:44 +0200 [thread overview]
Message-ID: <46727E7C.8060102@digadd.de> (raw)
Hi everyone,
I added a drive to a linux software RAID-5 last night. Now that worked
fine... until I changed the partition table.
Disk /dev/md_d5: 2499.9 GB, 2499990978560 bytes
2 heads, 4 sectors/track, 610349360 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id System
/dev/md_d5p1 1 244142 976566 83 Linux
/dev/md_d5p2 244143 5126956 19531256 8e Linux LVM
/dev/md_d5p3 5126957 488279488 1932610128 8e Linux LVM
This is how the layout looked before the changes.
Device Boot Start End Blocks Id System
/dev/md_d5p1 1 244142 976566 83 Linux
/dev/md_d5p2 244143 5126956 19531256 8e Linux LVM
/dev/md_d5p3 5126957 73478448 273405968 8e Linux LVM
This is how it looks now - the fdisk tools (fdisk/cfdisk) are unable to
crate a single partition > 2TB. Of course now LVM complains that the PV
is too small:
WARNING: Physical Volume /dev/md_d5p3 is too large for underlying device
PV Size 260.74 GB / not usable 8192.00 EB
I was able to restore a somewhat close partition table now... Close
enough for the LVM to work correctly.
Device Boot Start End Blocks Id System
/dev/md_d5p1 1 244142 976566 83 Linux
/dev/md_d5p2 244143 5126956 19531256 8e Linux LVM
/dev/md_d5p3 5126957 488279495 1932610156 8e Linux LVM
/dev/md_d5p4 488279496 73478448 488279460 8e Linux LVM
Where is the inherent limit? The partitioning software, or partitioning
all by itself?
Regards,
Christian
next reply other threads:[~2007-06-15 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 11:56 Christian Schmidt [this message]
2007-06-15 14:37 ` Help needed: Partitioned software raid > 2TB Andi Kleen
2007-06-15 14:03 ` Christian Schmidt
2007-06-15 16:25 ` Jan Engelhardt
2007-06-16 5:38 ` Alexander E. Patrakov
2007-06-16 6:46 ` Jan Engelhardt
2007-06-16 7:55 ` Alexander E. Patrakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46727E7C.8060102@digadd.de \
--to=lkml@digadd.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.