From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lAPHJbkI028586 for ; Sun, 25 Nov 2007 12:19:37 -0500 Received: from smtp105.plus.mail.mud.yahoo.com (smtp105.plus.mail.mud.yahoo.com [68.142.206.238]) by mx3.redhat.com (8.13.1/8.13.1) with SMTP id lAPHJ6lc027860 for ; Sun, 25 Nov 2007 12:19:06 -0500 From: "Jonathan Gauntt" Subject: [linux-lvm] Maximum Physical volume size? Date: Sun, 25 Nov 2007 11:18:56 -0600 Message-ID: <000001c82f87$44e974a0$cebc5de0$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C82F54.FA4F04A0" Content-Language: en-us Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: linux-lvm@redhat.com This is a multipart message in MIME format. ------=_NextPart_000_0001_01C82F54.FA4F04A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello - were you able to resolve? I have the exact same error with same volume size. Jonathan Thomas, Charles Norton wrote: > I seem to be exceeding a limit somewhere when I attempt to install a > RedHat Linux Client release 5 O/S on a 2.8 Terabyte Physical disk. The > install goes without error and creates a Volume group and logical > volumes for the O/S partitions and the balance of the space as a 2.6 > Terabyte logical volume. When I reviewed the ?partitioning? I attempted > to reduce the size of the of the 2.6 Terabyte Logical Volume a little so > I could add a little to the root Logical Volume. It refused to change > the size and claimed that the reduced size exceeded the maximum size > limit of 2 Terabytes. I decided to press on without making the change. > When I booted up the new O/S the VolumeGroup00 was discovered but > device-mapper reported: > Do you have the logs generated by anaconda available still? These are placed into /var/log/anaconda* and /root/install.log*. There should also be a file named /root/anaconda-ks.cfg which has the kickstart commands to re-create the storage configuration used in the install. This would let us see what anaconda had tried to configure on the system. If you can boot the machine into rescue mode and generate an lvmdump tarball that would also be helpful. Do you have somewhere you could post those online? That would be better than sending large attachments to the list. Kind regards, Bryn. ------=_NextPart_000_0001_01C82F54.FA4F04A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello – were you able to resolve?  I = have the exact same error with same volume size.

 

 

Jonathan

 

 

Thomas, Charles Norton wrote:
> I seem to be exceeding a limit somewhere when I attempt to install = a
> RedHat Linux Client release 5 O/S on a 2.8 Terabyte Physical disk. = The
> install goes without error and creates a Volume group and logical =
> volumes for the O/S partitions and the balance of the space as a = 2.6
> Terabyte logical volume. When I reviewed the ?partitioning? I = attempted
> to reduce the size of the of the 2.6 Terabyte Logical Volume a = little so
> I could add a little to the root Logical Volume. It refused to = change
> the size and claimed that the reduced size exceeded the maximum = size
> limit of 2 Terabytes. I decided to press on without making the = change.
> When I booted up the new O/S the VolumeGroup00 was discovered but =
> device-mapper reported:
>

Do you have the logs generated by anaconda available still? These are =
placed into /var/log/anaconda* and /root/install.log*. There should also =
be a file named /root/anaconda-ks.cfg which has the kickstart commands =
to re-create the storage configuration used in the install.

This would let us see what anaconda had tried to configure on the = system.

If you can boot the machine into rescue mode and generate an lvmdump =
tarball that would also be helpful.

Do you have somewhere you could post those online? That would be better =
than sending large attachments to the list.

Kind regards,
Bryn.

------=_NextPart_000_0001_01C82F54.FA4F04A0--