Btrfs: Difference between revisions

Revision as of 05:41, 7 September 2020

In other languages: English (en) italiano (it) [edit]

Btrfs: the b-tree filesystem

Btrfs is a copy-on-write filesystem for Linux aimed at implementing advanced features including error detection, fault tolerance, recovery, transparent compression, cheap snapshots, integrated volume management, and easy administration. It provides multiple device storage pooling, RAID-like functionality, fast snapshot creation, and checksumming of data and metadata. Contributors include Facebook, Fujitsu, (open)SUSE, Oracle, and Western Digital. Btrfs is licensed under the GPL and open for contribution from anyone.

Default filesystem, on the desktop

Btrfs is the default file system for desktops, starting with Fedora 33. See the Change Proposal
Fedora Magazine: Btrfs Coming to Fedora 33

Reporting bugs

Bugs related to btrfs user-space commands should be filed against the btrfs-progs component.
All other bugs should be filed against the kernel component. Following submission of the bug, please set the Assignee field to: fedora-kernel-btrfs@fedoraproject.org and Save the change.

Installer support

The Fedora installer, Anaconda, uses Btrfs by default in desktop editions and spins; and as an option in Manual Partitioning for Server, Cloud, and IoT editions. Fedora CoreOS installer, Ignition, also supports Btrfs as an option.
The Btrfs partition scheme preset creates an ext4 /boot, and a Btrfs pool. Two subvolumes, root and home, are created from that pool and mounted at / and /home respectively.
Additional mount points using Btrfs will also have corresponding subvolumes created based on the Name field. Subvolumes do not have a size, so the Desired Capacity field when creating new mount points is ignored and can be left blank.

Btrfs commands for LVM users

Chart of LVM commands and their Btrfs approximates

Advanced and developer related material

Conversions from Ext3/Ext4 volumes to Btrfs (and back!)

Although Btrfs does not need LVM, if you already are using it then converting your volume does not remove LVM. It also doesn't create the subvolume layout that we're using in Anaconda, and image builders.

Btrfs Wiki has more information on conversion and rollback.

Upstream Development

@@ Line 1: / Line 1: @@
-= Btrfs filesystem =
+{{autolang|base=yes}}
-== Summary ==
+===Btrfs: the b-tree filesystem===
-Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance, repair and easy administration. Initially developed by Oracle, Btrfs is licensed under the GPL and open for contribution from anyone.
+Btrfs is a copy-on-write filesystem for Linux aimed at implementing advanced features including error detection, fault tolerance, recovery, transparent compression, cheap snapshots, integrated volume management, and easy administration. It provides multiple device storage pooling, RAID-like functionality, fast snapshot creation, and checksumming of data and metadata. Contributors include Facebook, Fujitsu, (open)SUSE, Oracle, and Western Digital. Btrfs is licensed under the GPL and open for contribution from anyone.
-For more detailed information can be found at the [http://btrfs.wiki.kernel.org Btrfs homepage].
+===Default filesystem, on the desktop===
+* Btrfs is the default file system for desktops, starting with Fedora 33. See the [https://fedoraproject.org/wiki/Changes/BtrfsByDefault Change Proposal]
+* [https://fedoramagazine.org/btrfs-coming-to-fedora-33/ Fedora Magazine: Btrfs Coming to Fedora 33]
-== Purpose ==
+===Reporting bugs===
-The purpose of this page is not to duplicate information that can be found on other sites both internal and external but to consolidate and organize information and to make it Fedora specific where appropriate.
+* Bugs related to <code>btrfs</code> user-space commands should be filed against the <span style="color: blue">btrfs-progs</span> component.
+* All other bugs should be filed against the <span style="color: blue">kernel</span> component. Following submission of the bug, please set the Assignee field to: <span style="color: blue">fedora-kernel-btrfs@fedoraproject.org</span> and Save the change.
-== Btrfs support in Fedora ==
+===Installer support===
-* Btrfs has been available for testing as early as Fedora 11 but required a special boot parameter to be passed to Anaconda during installation.
+* The Fedora installer, Anaconda, uses Btrfs by default in desktop editions and spins; and as an option in Manual Partitioning for Server, Cloud, and IoT editions. Fedora CoreOS installer, Ignition, also supports Btrfs as an option.
+* The Btrfs partition scheme preset creates an ext4 /boot, and a Btrfs pool. Two subvolumes, root and home, are created from that pool and mounted at / and /home respectively.
+* Additional mount points using Btrfs will also have corresponding subvolumes created based on the Name field. Subvolumes do not have a size, so the Desired Capacity field when creating new mount points is ignored and can be left blank.
-== Frequently Asked Questions ==
+===Recommended reading for users===
-* Why use (or not use) Btrfs?
+* `man 5 btrfs` — info about btrfs itself: mount options, features, limits, swapfile support, the case of multiple block group profiles
-** The subvolume capability negates the need for LVM.
+* `man btrfs` — btrfs user space commands overview
-** Filesystem based [https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices RAID 0/1/10].
+* `man btrfs <command>` — man page for this specific btrfs command, e.g. `man btrfs device`. NOTE: Any command name can be shortened so long as the shortened form is unambiguous, e.g. `btrfs fi us` is equivalent to `btrfs filesystem usage`.
-** Online resizing and addition/removal of disks.
+* `man mkfs.btrfs` — man page for the mkfs command, includes info on block groups, chunks, raid, multiple device layouts, profiles, redundancy, space utilization, and minimum devices.
-** Btrfs is slated to be the default filesystem in Fedora 16.
+* [https://raid.wiki.kernel.org/index.php/Timeout_Mismatch linux-raid@ list: Timeout Mismatch]
-** Btrfs currently has limited fsck capability so make sure you backup your data!
+* [https://lore.kernel.org/linux-btrfs/20200627032414.GX10769@hungrycats.org/ linux-btrfs@ list: How to use btrfs raid5 successfully(ish)]
-* How to convert Ext3/Ext4 volumes to Btrfs (and back!)
+===Btrfs commands for LVM users===
+* [https://fedoraproject.org/wiki/User:Chrismurphy/lvm2btrfs Chart of LVM commands and their Btrfs approximates]
-== External Documentation ==
+===Advanced and developer related material===
-*
+* [https://github.com/btrfs/btrfs-dev-docs Collection of documents that describe internals of the BTRFS filesystem.]
+* [https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ Btrfs Wiki: Developer's FAQ, contributing to Btrfs.]
+===Conversions from Ext3/Ext4 volumes to Btrfs (and back!)===
+{{admon/important|Although Btrfs does not need LVM, if you already are using it then converting your volume does not remove LVM. It also doesn't create the subvolume layout that we're using in Anaconda, and image builders.}}
+* Btrfs Wiki has more information on [https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3 conversion and rollback.]
+===Upstream Development===
+* [https://btrfs.wiki.kernel.org/index.php/Changelog Btrfs Changelog].
+* [https://btrfs.wiki.kernel.org/index.php/Status Stability status].
+* [https://btrfs.wiki.kernel.org/index.php/Btrfs_mailing_list Mailing list information].
+[[Category:btrfs|btrfs]]

Search