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.

Bug 1322273

Summary: kickstart fails with raid5 44TiB disk setup on RHEL 7.1
Product: Red Hat Enterprise Linux 7 Reporter: Hidehiko Matsumoto <hmatsumo>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: dlehman, hmatsumo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-27 16:16:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hidehiko Matsumoto 2016-03-30 07:51:37 UTC
Description of problem:
The customer got the following messages when they install RHEL with raid5 44TiB disk.

~~~
Not enough space in file systems for the current software selection.An additional 1998.98 MiB is needed.
Please make your choice from above ['q' to quit | 'b' to begin installation | 'r' to refresh]
~~~


Version-Release number of selected component (if applicable):
anaconda-19.31.123-1.el7


How reproducible:
100%


Steps to Reproduce:
The customer used the following configuration for kickstart with raid5 44TiB disk.

~~~
bootloader --location=mbr --boot-drive=sda
zerombr
clearpart --all --initlabel --drives=sda
part biosboot --fstype="biosboot" --ondisk=sda --size=1 --label=biosboot
part /boot --fstype="xfs" --ondisk=sda --size=1024 --fsoptions="defaults,noatime" --label=boot
part swap --fstype="swap" --ondisk=sda --recommended --label=swap
part / --fstype="xfs" --grow --ondisk=sda --size=10240 --fsoptions="defaults,noatime" --label=root
~~~


Actual results:
Not enough space in file systems for the current software selection.An additional 1998.98 MiB is needed.
Please make your choice from above ['q' to quit | 'b' to begin installation | 'r' to refresh]


Expected results:
Space is available and installable


Additional info:
The customer tried to test the following Fedora rawhide with raid5 44TiB disk.

~~~
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/x86_64/os/images/
~~~

And they could install Fedora rawhide.

Comment 2 David Lehman 2016-03-31 13:30:23 UTC
Please attach the logs from /tmp, collected after the failure occurs. Thank you.

Comment 9 Brian Lane 2016-05-27 16:16:59 UTC
This may be related to bug 1320436, which has been fixed in anaconda-21.48.22.66-1 but without the logs and the kickstart it is impossible to tell for sure.