Thanks for bugzilla link, i missed it.
On 08/14/2014 01:00 AM, Maxim Shpakov wrote:
Just want to mention that this behaviour is already known bug
https://bugzilla.redhat.com/show_bug.cgi?id=1093144#c7
2014-07-31 12:01 GMT+03:00 Maxim Shpakov ma...@osetia.org:
Hi!
I can confirm this.
Just want to mention that this behaviour is already known bug
https://bugzilla.redhat.com/show_bug.cgi?id=1093144#c7
2014-07-31 12:01 GMT+03:00 Maxim Shpakov ma...@osetia.org:
Hi!
I can confirm this.
--grow on LVM partition is broken for raid+lvm kickstart installs.
bootloader
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=200 --ondisk=sda
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.
4 matches
Mail list logo