Hide Forgot
Description of problem: Anaconda gives an exception with error contained therein lv is too large to fit in free space when doing kickstart with RAID/LVM setup Version-Release number of selected component (if applicable): fc13 How reproducible: 100% Steps to Reproduce: 1. ks.cfg has this in it: part raid.01 --size=256 --ondisk=sda part raid.02 --size=256 --ondisk=sdb part raid.03 --size=1 --grow --ondisk=sda part raid.04 --size=1 --grow --ondisk=sdb raid /boot --fstype ext3 --level=RAID1 --device=md0 raid.01 raid.02 raid pv.01 --fstype ext3 --level=RAID1 --device=md1 raid.03 raid.04 volgroup VolGroup00 pv.01 logvol swap --fstype swap --name=LogVol00 --vgname=VolGroup00 --size=4096 logvol /lvmbackup --fstype ext3 --name=backup --vgname=VolGroup00 --size=4096 logvol / --fstype ext4 --name=LogVol01 --vgname=VolGroup00 --size=1 --grow and the server (Sun Fire X2100 M2) has 2 x 250G SATA disks 2. 3. Actual results: Expected results: successful kick Additional info: Looks to be identical to bug reported against FC11. https://bugzilla.redhat.com/show_bug.cgi?id=495247 Workaround is to change --size=1 to --size=50000 in the part... grow config. ie: part raid.03 --size=50000 --grow --ondisk=sda part raid.04 --size=50000 --grow --ondisk=sdb
Right, as you mentioned, you should use --size= parameters that are reasonable by default and then --grow from there. Using --size=1 --grow is no longer recommended.