Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 621841 - kickstart fails with lv is too large to fit in free space
kickstart fails with lv is too large to fit in free space
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-06 05:12 EDT by Ian Donaldson
Modified: 2011-05-05 06:02 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-06 10:07:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ian Donaldson 2010-08-06 05:12:44 EDT
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):


How reproducible:


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

Actual results:

Expected results:

successful kick

Additional info:

Looks to be identical to bug reported against FC11.

Workaround is to change --size=1 to --size=50000 in the part... grow config.


part raid.03 --size=50000 --grow --ondisk=sda
part raid.04 --size=50000 --grow --ondisk=sdb
Comment 1 Chris Lumens 2010-08-06 10:07:42 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.