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:
Can't create volumes larger than 16T. Even with xfs.
Version-Release number of selected component (if applicable):
13.21.176-1.el6.centos
How reproducible:
Always.
Steps to Reproduce:
1. Create kickstart with volume larger than 16T
Actual results:
Error showing that maximum possible volume can be 16T
Expected results:
Volume created and formatted without any problem
Additional info:
I know that RHEL 6 e2fsprogs doesn't allow to create >16T ext4 partition, but xfs is possible. mkfs.xfs works without any problem on partitions larger than 16T, but Anaconda doesn't allow it anyway.
Created attachment 653555[details]
Screenshot from iKVM with anaconda error
My line in kickstart:
part /mnt/storage --noformat --onpart=sdc1 --fstype xfs --label storage
Partition was created in previous installation. It's 65T.
Message attached.
BTW, does RHEL7 (I don't believe RHEL6.4) will support ext4 partitions larger than 16T? I know it needs newer e2fsprogs and fsck...
And those partitions limits will be larger later?
Comment 6RHEL Program Management
2013-05-06 21:14:25 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
reproduced on HREL6.4 x86_64 Server
verified on RHEL6.5-20131009.0 x86_64 Server
Also verified, that anaconda creates partition on whole (65T) device when used:
part /data --size 1 --grow --asprimary --fstype xfs --ondisk=vdb
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1588.html