Red Hat Bugzilla – Bug 880577
Anaconda can't create partitions larger than 16T
Last modified: 2015-09-27 22:06:32 EDT
Description of problem:
Can't create volumes larger than 16T. Even with xfs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create kickstart with volume larger than 16T
Error showing that maximum possible volume can be 16T
Volume created and formatted without any problem
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.
What is the exact error message you are seeing?
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.
Ah, I see. That number was based upon previous discussions about what is the maximum size we can support, but it looks like 100 TB is now the maximum supported size:
Easy to fix.
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?
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.
Adding qa_ack+, I'm able to reproduce this bug. No special HW is required, it's reproducible in virtual system.
Patch posted to anaconda-patches for review.
Patch pushed to rhel6-branch, commit 3fc54a69c6d3f1b9a5752dd67959b1196c37b66d.
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.