From Fedora Project Wiki

mNo edit summary
mNo edit summary
Line 17: Line 17:
* 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.
* 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.


===Installer===
===Support in installers===
* 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 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.
* 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.

Revision as of 03:56, 7 September 2020

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.

Upstream Development

Default filesystem, on the desktop

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.

Support in installers

  • 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.

Recommended reading for users

  • man 5 btrfs - info about btrfs itself: mount options, features, limits, swapfile support, the case of multiple block group profiles
  • man btrfs - btrfs user space commands overview
  • man btrfs <command> - man page for this specific btrfs command, e.g. man btrfs device
  • 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.
  • linux-raid@ list: Timeout Mismatch
  • linux-btrfs@ list: How to use btrfs raid5 successfully(ish)

Advanced and developer related material

Any command name can be shortened so long as the shortened form is unambiguous

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

Important.png
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.