(Created page with "<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. --...") |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 20: | Line 20: | ||
* Targeted release: [[Releases/17 | Fedora 17 ]] | * Targeted release: [[Releases/17 | Fedora 17 ]] | ||
* Last updated: 09 Jan 2012 | * Last updated: 09 Jan 2012 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 65: | Line 65: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* | * 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 == | == Release Notes == | ||
| Line 73: | Line 72: | ||
<!-- 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 e2fsprogs as soon as an update is available. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/F17Ext4Above16T]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
[[Category: | [[Category:FeatureAcceptedF17]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 16:26, 29 May 2012
Ext4 support beyond 16T
Summary
Support Ext4 filesystems larger than 16 terabytes.
Owner
- Name: Eric Sandeen
- Email: sandeen@redhat.com
Current status
- Targeted release: Fedora 17
- Last updated: 09 Jan 2012
- Percentage of completion: 100%
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 e2fsprogs as soon as an update is available.