Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The RHEL 6 Installation Guide Advanced Partitioning Example shows creating a RAID partition with '--size=1 --grow':
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html#s2-kickstart2-options-part-examples
This can result in Anaconda tracebacks and the error "new lv is too large to fit in free space" as shown in bug 677915.
Furthermore, as mentioned in bug 677915 comment 4:
Second, the use of growable raid partitions is problematic as we make no
guarantees that the various raid partitions will end up with sizes that
please mdadm when the time comes to create the array. Fixed sizes are
strongly recommended for software raid partitions.
The initial size should be larger than the sum of logical volumes or filesystems that will be on the partition. In the example shown, there are two logical volumes 8000 MiB each, plus a third logical volume at least 1 MiB, so the RAID partitions should be 16001 plus some extra for overhead, so 16384 should be a good starting place:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
part raid.15 --size 16384 --grow --ondrive=hda
...
part raid.25 --size 16384 --grow --ondrive=hdc
...
raid pv.01 --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25
...
volgroup sysvg pv.01
logvol /var --vgname=sysvg --size=8000 --name=var
logvol /var/freespace --vgname=sysvg --size=8000 --name=freespacetouse
logvol /usr/local --vgname=sysvg --size=1 --grow --name=usrlocal
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please update the Installation Guide to use larger starting sizes for growable partitions.