Bug 789112 - We would like >16tb support in e2fsprogs
Summary: We would like >16tb support in e2fsprogs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: e2fsprogs
Version: 6.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Eric Sandeen
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-09 20:34 UTC by Chris Pepper
Modified: 2012-02-17 23:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 23:45:33 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chris Pepper 2012-02-09 20:34:27 UTC
Description of problem:
e2fsprogs v1.42 adds the ability to create filesystems of 16tb and larger.
We would like v1.42, or at least backport of its large filesystem support, in RHEL 6.

Version-Release number of selected component (if applicable):
RHEL 6.2 has v1.41, and presumably doesn't have a backport of large filesystem support as I haven't seen anything about this in the release notes.

How reproducible:
Always.

Steps to Reproduce:
1. Attempt to create a filesystem of 16tb or larger on an array.
  
Actual results:
mkfs.ext4 fails.

Expected results:
With e2fsprogs v1.42, mkfs.ext4 should work

Comment 2 Eric Sandeen 2012-02-09 21:46:35 UTC
e2fsprogs-1.42 was a massive change to e2fsprogs compared to the RHEL6 codebase:

 471 files changed, 44469 insertions(+), 14822 deletions(-)

Those changes do not yet have sufficient testing or real-world experience to warrant enterprise support.  It is also not yet complete; for example resize support is not there.

In RHEL6, if you need > 16T, XFS is available and scales very well for large filesystems.

Comment 3 Eric Sandeen 2012-02-17 23:45:33 UTC
For now, in RHEL6 this is WONTFIX.  If upstream gets to the point where >16T is feasible on ext4, we can re-open and/or re-consider this one.  Today, XFS is available and robust for these usecases.


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