FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 11-11-2010, 06:54 PM
Eric Smith
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

I just tried to install F14 on a new server with a 7.6 TB RAID (five
Hitachi 2 TB drives on a 3ware 9750). I was pleased to see that the
disk partitioning interface in Anaconda recognized the array and didn't
have a problem with the size, reporting it as 7629352 MB. Unfortunately
it won't let me create an LVM PV larger than 2 TB (2095151 MB). And if
I try to create two PVs, it limits them to 1 TB each.

Is there any good reason to have this limit, or should I report it as a
bug against Anaconda (or some other component)?

Thanks,
Eric

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-11-2010, 07:13 PM
"Richard W.M. Jones"
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

On Thu, Nov 11, 2010 at 11:54:54AM -0800, Eric Smith wrote:
> I just tried to install F14 on a new server with a 7.6 TB RAID (five
> Hitachi 2 TB drives on a 3ware 9750). I was pleased to see that the
> disk partitioning interface in Anaconda recognized the array and didn't
> have a problem with the size, reporting it as 7629352 MB. Unfortunately
> it won't let me create an LVM PV larger than 2 TB (2095151 MB). And if
> I try to create two PVs, it limits them to 1 TB each.
>
> Is there any good reason to have this limit, or should I report it as a
> bug against Anaconda (or some other component)?

I'm assuming this is because of MBR, and yes, it's a bug that really
really needs to be fixed because you can now buy at retail cheap disks
which are 2TB and larger. I think this is the bug:

https://bugzilla.redhat.com/show_bug.cgi?id=574551

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-11-2010, 08:22 PM
Michael Cronenworth
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

Eric Smith wrote:
> Is there any good reason to have this limit, or should I report it as a
> bug against Anaconda (or some other component)?
>

Must be a new thing. I installed Fedora 11 on a server with an 8TB raid
and it created a PV >2TB on its own.


# pvscan
PV /dev/sda2 VG VolGroup00 lvm2 [1.95 TiB / 64.00 MiB free]
PV /dev/sdb1 VG VolGroup00 lvm2 [6.23 TiB / 0 free]
Total: 2 [8.19 TiB] / in use: 2 [8.19 TiB] / in no VG: 0 [0 ]
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-12-2010, 06:50 AM
Zoltan Boszormenyi
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

Hi,

2010-11-11 20:54 keltezéssel, Eric Smith írta:
> I just tried to install F14 on a new server with a 7.6 TB RAID (five
> Hitachi 2 TB drives on a 3ware 9750). I was pleased to see that the
> disk partitioning interface in Anaconda recognized the array and didn't
> have a problem with the size, reporting it as 7629352 MB. Unfortunately
> it won't let me create an LVM PV larger than 2 TB (2095151 MB). And if
> I try to create two PVs, it limits them to 1 TB each.
>
> Is there any good reason to have this limit, or should I report it as a
> bug against Anaconda (or some other component)?
>
> Thanks,
> Eric

I run into the same problem with installing F14 but fortunately
it's easily solvable. I have split my 3.6TB RAID10 array into
a 150GB boot volume plus the "rest". I wanted to put /home
to the 3.45TB volume but anaconda wanted to create an
MSDOS partition by default. The 150GB volume is bootable
from the BIOS, no problem, /boot, / and swap was put there.
I had to press Ctrl-Alt-F2 and used "parted" on the console
to create the GPT disklabel on the large volume and created
one partition covering it all. Then used anaconda to accept
the already existing partitions and used the large partition
for /home. Ext4 had no problems formatting it.

Best regards,
Zoltán Böszörményi

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-12-2010, 07:28 AM
Hans de Goede
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

Hi,

On 11/11/2010 08:54 PM, Eric Smith wrote:
> I just tried to install F14 on a new server with a 7.6 TB RAID (five
> Hitachi 2 TB drives on a 3ware 9750). I was pleased to see that the
> disk partitioning interface in Anaconda recognized the array and didn't
> have a problem with the size, reporting it as 7629352 MB. Unfortunately
> it won't let me create an LVM PV larger than 2 TB (2095151 MB). And if
> I try to create two PVs, it limits them to 1 TB each.
>
> Is there any good reason to have this limit, or should I report it as a
> bug against Anaconda (or some other component)?

The problem is that msdos disklabels / partition tables stink. The solution
is to use a gpt partition table. anaconda defaults to creating a msdos
disklabel when no disklabel is found on non EFI machines, because not all
BIOS' will boot from gpt labelled disks. Anaconda will use an existing
gpt disklabel if found. So the solution / workaround in your case is
to create a gpt disklabel before running the installer.

Boot the installer into rescue mode and run
parted /dev/<path-to-entire-disk>

And in parted do:
mklabel gpt

The reboot into the regular installer and you should be able to use the entire
disk <note this will destroy everything which you currently have on the disk>.

I guess that maybe anaconda needs to be changed to create a gpt disklabel
when the disk > 2TB, and no disklabel is present.

Which leaves the question did anaconda create the disklabel or was one already
present (iow did it ask to initialize the disk)?

Anyways the proper place to further discuss this is in a bugzilla ticket.

Regards,

Hans (ex anaconda developer)
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 11-13-2010, 10:27 PM
"Richard W.M. Jones"
 
Default still a 2TB limit in F14 Anaconda, for LVM PV size

On Fri, Nov 12, 2010 at 09:28:06AM +0100, Hans de Goede wrote:
> Boot the installer into rescue mode and run
> parted /dev/<path-to-entire-disk>
>
> And in parted do:
> mklabel gpt

For VMs you can do:

guestfish -a /dev/<path-to-VM-disk> run : part-init gpt

(which destroys any data on /dev/<path-to-VM-disk>), and then proceed
with virt-install/whatever as usual.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 08:53 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org