Anaconda, Kickstart, Lvm Over Raid, Logvol –grow, CentOS7 Mystery
I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid.
If i am using “logvol –grow i get “ValueError: not enough free space in volume group”
Only workaround i can find is to add –maxsize=XXX where XXX is at least 640MB less than available.
(10 extents or 320Mb per created logical volume)
Following snippet is failing with “DEBUG blivet: failed to set size: 640MB short”
part raid.01 –size 512 –asprimary –ondrive=sda part raid.02 –size 1 –asprimary –ondrive=sda –grow part raid.11 –size 512 –asprimary –ondrive=sdb part raid.12 –size 1 –asprimary –ondrive=sdb –grow raid /boot –fstype=”xfs” –device=”md0″ –level=RAID1 raid.01 raid.11
raid pv.01 –fstype=”lvmpv” –device=”md1″ –level=RAID1 raid.02 raid.12
volgroup vg0 pv.01
logvol / –fstype=”xfs” –grow –size@96 –name=lvRoot –vgname=vg0
logvol swap –fstype=”swap” –size 48 –name=lvSwap –vgname=vg0
If i only add –maxsize164 everything is working.
(but after install i have 640MB in 20 Free PE in vg0, for details see “after –maxsize install”)
logvol / –fstype=”xfs” –grow –size@96 –name=lvRoot –vgname=vg0
——changed to —–>
logvol / –fstype=”xfs” –grow –size@96 –name=lvRoot –vgname=vg0 –maxsize164
Some interesting DEBUG lines :
should it be 11744 or there is 320MB overhead ?
320MB missing again, total of 640MB
nice, i have 9056MB free in vg0 (640MB short but still … )
wtf, who is counting what !!
Could anyone shed some light ?
P.S.
“after –maxsize install”
========================If i limit root logvol with –maxsize164, after installation i get 640MB of free space (20 Free PE).
Missing 640Mb is free according to lvm :
[root@c7-pxe-install ~]# pvdisplay
— Physical volume –
3 thoughts on - Anaconda, Kickstart, Lvm Over Raid, Logvol –grow, CentOS7 Mystery
Hi!
I can confirm this.
–grow on LVM partition is broken for raid+lvm kickstart installs.
bootloader –location=mbr –driveorder=sda,sdb –append=”net.ifnames=0
crashkernel=auto rhgb quiet”
zerombr clearpart –all –drives=sda,sdb –initlabel
part raid.1 –asprimary –size 0 –ondisk=sda part raid.2 –size=1 –grow –ondisk=sda part raid.3 –asprimary –size 0 –ondisk=sdb part raid.4 –size=1 –grow –ondisk=sdb
raid /boot –fstype=ext4 –level=RAID1 –device=md0 raid.1 raid.3
raid pv.1 –level=RAID1 –device=md1 raid.2 raid.4
volgroup vg0 –pesizee536 pv.1
logvol swap –name=swap –vgname=vg0 –size@96
logvol /tmp –fstype=ext4 –name=tmp –vgname=vg0 –size@96
–fsoptions=”noexec,nosuid,nodev,noatime”
logvol / –fstype=ext4 –name=root –vgname=vg0 –size240 –grow
–fsoptions=”defaults,noatime”
Such partitioning scheme is now working. Anaconda is complaining about
“ValueError: not enough free space in volume group”
Buf if I remove –grow from last logvol – everything is ok.
I don’t understand what I’m doing wrong, such kickstart works flawlessly for C6 installs.
2014-07-16 14:21 GMT+03:00 Borislav Andric:
Just want to mention that this behaviour is already known bug
https://bugzilla.redhat.com/show_bug.cgi?id93144#c7
2014-07-31 12:01 GMT+03:00 Maxim Shpakov:
Thanks for bugzilla link, i missed it.