<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->

<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->

* Ext4 filesystems are now capable of greater than 16T.

* Ext4 filesystems are now capable of greater than 16T.

+

+

* The GA version of e2fsprogs in F17 (e2fsprogs-1.42-4.fc17) contains some bugs related to filesystems above 16T, primarily related to e2fsck. Running e2fsck on these large filesystems may induce corruption. Users with > 16T ext4 filesystems are advised to upgrade e2fsprog as soon as an update is available.

Summary

Owner

Current status

Detailed Description

Previous Fedora releases have been limited to 16T (or more exactly, 2^32 filesystem blocks) maximum filesystem sizes on ext4. The recent e2fsprogs-1.42 release upstream has lifted this limitation, and the desire is to scale ext4 to 100T maximum filesystem size. While code is generally in place, testing and verification will be useful.

Benefit to Fedora

16T is also known as "A raid of a few cheap commodity 3T drives" and is just not that big today. Users will be running into the 16T limits of Ext4, and while Fedora ships non-default filesystems like XFS which can handle this without any trouble, we should improve our default filesystem to function at these sizes as well.

Scope

e2fsprogs-1.42 has already been released with initial support greater than 16T, and kernel code already has support as well. There are rough edges to work out, and there is testing to be done.

How To Test

Ideally, stress testing on actual storage of significant size. However, we can also make use of things like sparse loopback files or dm targets to facilitate testing when large storage is not available. The xfstests test suite can do some work on large loopback files, for example.

User Experience

No significant changes, other than the ability to mkfs, mount, and administer larger ext4 filesystems.

Dependencies

None.

Contingency Plan

If significant issues are encountered, we could locally patch e2fsprogs-1.42 and beyond to disallow larger filesystems.

Documentation

Because this is primarily an enhancement of existing capability, very little documentation should be required, unless we run into significant caveats for use.

Release Notes

Ext4 filesystems are now capable of greater than 16T.

The GA version of e2fsprogs in F17 (e2fsprogs-1.42-4.fc17) contains some bugs related to filesystems above 16T, primarily related to e2fsck. Running e2fsck on these large filesystems may induce corruption. Users with > 16T ext4 filesystems are advised to upgrade e2fsprog as soon as an update is available.