Red Hat Bugzilla – Bug 493753
F11 beta installer limits LVM volume group extent size to 4MB
Last modified: 2009-06-25 13:52:34 EDT
I'm installing F11 beta on a virtual guest. I've given the guest a 16GB (virtual) disk.
I choose a custom disk layout in anaconda. I create a /boot partition that is 1024MB in size. I then create an LVM partition that consumes the rest of the drive.
I then go to create logical volumes. The "Make LVM Volume Group" screen appears. The default physical extent size defaults to 4 MB. When I attempt to change it to 32MB instead, I receive this pop-up error message:
The physical extent size cannot be changed because
the value selected ( 32.00 MB) is larger than the
smallest physical volume ( -32.00 MB) in the volume
This is pretty clearly a bug, as I can jump to the command line and manually partition the disk (include creating volume groups) just fine.
A correction: I can increase the size to 8MB without getting the error pop-up, but no larger.
This should be fixed in anaconda-22.214.171.124-1.
*** Bug 496673 has been marked as a duplicate of this bug. ***
I just downloaded the Fedora 11 preview release, and it's still having the same problem, with anaconda 126.96.36.199.
I'm installing it in a VMware Server guest on an 8GB virtual disk, and I did a custom layout with a 100MB /boot, 1024MB swap, and the rest LVM. I get the same error message described above whenever I try to go above 4MB extents (which is what it defaults to).
(In reply to comment #4)
> I just downloaded the Fedora 11 preview release, and it's still having the same
> problem, with anaconda 188.8.131.52.
> I'm installing it in a VMware Server guest on an 8GB virtual disk, and I did a
> custom layout with a 100MB /boot, 1024MB swap, and the rest LVM. I get the
> same error message described above whenever I try to go above 4MB extents
> (which is what it defaults to).
This is expected behavior if the VG is fully allocated when you try to change the extent size.
If you want to increase the extent size, you must first remove one of the logical volumes so there is free space in the volume group. Then, once you have changed the extent size, you can add the additional logical volume.
Confirmed (comment #4), for an interactive install of Fedora 11 Preview (x86_64; anaconda 184.108.40.206).
However, if you perform a kickstart install, you can set a 32MB block size just fine, via these partitioning commands:
clearpart --drives=vda --all --initlabel
part /boot --ondisk=vda --fstype ext3 --size=1024
part pv.0 --ondisk=vda --size=1024 --grow
volgroup vos --pesize=32768 pv.0
logvol swap --fstype swap --name=swap --vgname=vos --size=2048
logvol / --fstype ext4 --name=root --vgname=vos --size=1024
logvol /usr --fstype ext4 --name=usr --vgname=vos --size=4096
logvol /home --fstype ext4 --name=home --vgname=vos --size=1024
logvol /var --fstype ext4 --name=var --vgname=vos --size=1024
logvol /var/tmp --fstype ext4 --name=vtmp --vgname=vos --size=1024
logvol /tmp --fstype ext4 --name=tmp --vgname=vos --size=1024
logvol /var/log --fstype ext4 --name=log --vgname=vos --size=1024
Dave, I don't understand what you mean about "expected behavior" (comment #5). If I create a new LVM partition, and then edit it, I cannot change the VG size above 8MB even if the VG has no logical volumes in it.
(In reply to comment #6)
> Confirmed (comment #4), for an interactive install of Fedora 11 Preview
> (x86_64; anaconda 220.127.116.11).
> Dave, I don't understand what you mean about "expected behavior" (comment #5).
> If I create a new LVM partition, and then edit it, I cannot change the VG size
> above 8MB even if the VG has no logical volumes in it.
Are you creating a new volume group or using one that already exists? I assume that by "create a new LVM partition, and then edit it" you mean you created an lvm partition and then created/edited a new volume group. Is this correct? And by "change the VG size" you mean change the VG's extent size, right?
I have created new volume groups with extent sizes of 32, 64, and 128 MB today without any problems. What exactly does the error message say? Can you attach the files /tmp/storage.log and /tmp/anaconda.log from the install attempt?
Created attachment 342503 [details]
screenshot of LVM pesize problem
Here's how to reproduce the problem:
Boot the installation DVD.
For the partitioning selection screen, select "Create custom layout".
On the next screen, create a 1GB /boot partition.
In the remaining space, create an LVM volume that fills to the maximum allowable size.
Click the "LVM" button.
In the "Make LVM Volume Group window", attempt to change the "Physical Extent" size above 8MB. It will fail.
Created attachment 342504 [details]
anaconda.log from failed pesize attempt
Created attachment 342505 [details]
storage.log from failed pesize attempt
Created attachment 342563 [details]
updates with proposed fix
Please try the attached updates.img and see if the problem persists.
I've seen this bug on multiple machines.
The proposed fix worked for me on the only machine I've tried so far.
More annoying was that anaconda only accepted the update if I put it on an ftp server. It refused it on any floppy created in accordance with http://fedoraproject.org/wiki/Anaconda/Updates. (But that's a different bug, eh?)
Confirmed that the proposed fix worked on my virtual machine (VMWare Server 1.0.6), using my web server (http) to provide the update. Anaconda allowed me to choose any of the extent sizes in the drop-down without an error message. I chose 32MB and successfully completed the install.
[root@f11pre ~]# vgdisplay
--- Volume group ---
VG Name vg_f11pre
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 6.88 GB
PE Size 32.00 MB
Total PE 220
Alloc PE / Size 219 / 6.84 GB
Free PE / Size 1 / 32.00 MB
VG UUID txQyqe-QxxQ-rBAq-xZ3u-rmZo-ZIaV-aYM70U
The latest fix will be included in anaconda-18.104.22.168-1.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here: