From Fedora Project Wiki
< Features
(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. --...') |
(moved back to FeaturePageIncomplete per email to devel-list, will see you again for F17 :)) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 19: | Line 19: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/16 | Fedora 16 ]] | * Targeted release: [[Releases/16 | Fedora 16 ]] | ||
* Last updated: | * Last updated: 2011-06-01 | ||
* Percentage of completion: 0% | * Percentage of completion: 0% | ||
| Line 40: | Line 40: | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Anaconda - not terribly important but would be good to expose some of the different features of BTRFS via anaconda. | * Anaconda - not terribly important but would be good to expose some of the different features of BTRFS via anaconda. | ||
* GRUB - would be good to have GRUB support for BTRFS, but if not we'd need to make sure Anaconda creates a /boot partition with ext3/4 so we can boot. | ** Subvolume support (for /home by default) | ||
** Optional compression | |||
** RAID support | |||
** Ext3/4 conversion | |||
* GRUB - would be good to have GRUB support for BTRFS, but if not we'd need to make sure Anaconda creates a /boot partition with ext3/4 so we can boot. (Grub2 or syslinux can natively boot btrfs) | |||
* LiveCD tools - these would need to be reworked to create a BTRFS image to install with. | * LiveCD tools - these would need to be reworked to create a BTRFS image to install with. | ||
| Line 66: | Line 70: | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
The change should be largely invisible to users. They will just be able to take advantage of the different features that BTRFS has if they so choose. | The change should be largely invisible to users. They will just be able to take advantage of the different features that BTRFS has if they so choose. | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
| Line 71: | Line 76: | ||
* Anaconda | * Anaconda | ||
* LiveCD tools | * LiveCD tools | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
| Line 77: | Line 83: | ||
== 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. --> | ||
* | *[http://btrfs.wiki.kernel.org/ | Btrfs Wiki] | ||
== Release Notes == | == Release Notes == | ||
| Line 85: | Line 91: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/F16BtrfsDefaultFs]] <!-- 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 --> | ||
* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=689509 | |||
[[Category:FeaturePageIncomplete]] | [[Category:FeaturePageIncomplete]] | ||
Latest revision as of 18:33, 8 August 2011
Fedora 16 BTRFS default file system
Summary
Make BTRFS the default file system for normal installs.
Owner
- Name: Josef Bacik
- Email: josef@redhat.com
Current status
- Targeted release: Fedora 16
- Last updated: 2011-06-01
- Percentage of completion: 0%
Detailed Description
Make BTRFS the default file system for new installations of Fedora, and use BTRFS's built in volume management capabilities instead of LVM.
Benefit to Fedora
BTRFS includes many features that do not exist in any other file system that are highly valuable to normal users, including
- Checksumming
- Snapshotting
- Built in volume management and RAID
Checksumming give our users better data integrity, and snapshotting allows us to do thing's like take snapshots of the file system before doing potentially dangerous things, like yum updates, in order to provide a position to roll back to.
Scope
- Anaconda - not terribly important but would be good to expose some of the different features of BTRFS via anaconda.
- Subvolume support (for /home by default)
- Optional compression
- RAID support
- Ext3/4 conversion
- GRUB - would be good to have GRUB support for BTRFS, but if not we'd need to make sure Anaconda creates a /boot partition with ext3/4 so we can boot. (Grub2 or syslinux can natively boot btrfs)
- LiveCD tools - these would need to be reworked to create a BTRFS image to install with.
How To Test
It should be simple enough to test, just do a normal install. If Anaconda gets support for the different BTRFS capabilities we'd want to test a couple of cases
- Single disk BTRFS
- Multi-disk BTRFS, RAID0/1/10
- Creating different subvolumes in the install
User Experience
The change should be largely invisible to users. They will just be able to take advantage of the different features that BTRFS has if they so choose.
Dependencies
- GRUB
- Anaconda
- LiveCD tools
Contingency Plan
We can just keep ext4 as the default installed file system.
Documentation
Release Notes
There shouldn't be anything we need to specifically say other than hi-light the change.