Btrfs is a modern copy on write (CoW) filesystem for Linux aimed at implementing advanced features while also focusing on fault tolerance, repair and easy administration. Jointly developed at multiple companies, Btrfs is licensed under the GPL and open for contribution from anyone. Not too many companies have said that they are using Btrfs in production, but we welcome those who can say so on the production users page.
For a feature status and stability please refer to the Status page. The filesystem disk format is stable; this means it is not expected to change unless there are very strong reasons to do so. If there is a format change, filesystems which implement the previous disk format will continue to be mountable and usable by newer kernels.
The Btrfs code base is under heavy development. Not only is every effort being made to ensure that it remains stable and fast but to make it more so with each and every commit. This rapid pace of development means that the filesystem improves noticeably with every new Linux release so it's highly recommended that users run the most modern kernel possible.
For benchmarks, it's recommended to test the latest stable Linux version, and not any older, as well as the latest Linux development versions. Also, it's recommended to test the various mount options such as different compression options.
As with all software, newly added features may need a few releases to stabilize.
If you find any behavior you suspect to be caused by a bug, performance issues, or have any questions about using Btrfs, please email the Btrfs mailing list (no subscription required). Please report bugs on Bugzilla.
Linux has a wealth of filesystems from which to choose, but we are facing a number of challenges with scaling to the large storage subsystems that are becoming common in today's data centers. Filesystems need to scale in their ability to address and manage large storage, and also in their ability to detect, repair and tolerate errors in the data stored on disk.
Major Features Currently Implemented
- Extent based file storage
- 2^64 byte == 16 EiB maximum file size (practical limit is 8 EiB due to Linux VFS)
- Space-efficient packing of small files
- Space-efficient indexed directories
- Dynamic inode allocation
- Writable snapshots, read-only snapshots
- Subvolumes (separate internal filesystem roots)
- Checksums on data and metadata (crc32c)
- Compression (zlib, LZO, ZSTD), heuristics
- Integrated multiple device support
- File Striping
- File Mirroring
- File Striping+Mirroring
- Single and Dual Parity implementations (experimental, not production-ready)
- SSD (flash storage) awareness (TRIM/Discard for reporting free blocks for reuse) and optimizations (e.g. avoiding unnecessary seek optimizations, sending writes in clusters, even if they are from unrelated files. This results in larger write operations and faster write throughput)
- Efficient incremental backup
- Background scrub process for finding and repairing errors of files with redundant copies
- Online filesystem defragmentation
- Offline filesystem check
- In-place conversion of existing ext2/3/4 and reiserfs file systems
- Seed devices. Create a (readonly) filesystem that acts as a template to seed other Btrfs filesystems. The original filesystem and devices are included as a readonly starting point for the new filesystem. Using copy on write, all modifications are stored on different devices; the original is unchanged.
- Subvolume-aware quota support
- Send/receive of subvolume changes
- Efficient incremental filesystem mirroring
- Batch, or out-of-band deduplication (happens after writes, not during)
Features by kernel version
As part of the changelog you can also review
Features Currently in Development or Planned for Future Implementation
- Online filesystem check
- Object-level mirroring and striping
- Alternative checksum algorithms
- In-band deduplication (happes during writes)
- Hot data tracking and moving to faster devices (or provided on the generic VFS layer)
- SMR support
- DAX/persistent memory support
- The file/directory -level encryption support (fscrypt)
News and Changelog
WARNING: kernels 4.14.25 - 4.14.27 and 4.15.8 - 4.15.9 on big endian machines will damage a filesystem after first umount. Little endian machines are unaffected. Please contact upstream developers if your filesystems were affected, the problem can be manually fixed and is only in the superblock, not data or regular metadata.
Linux v4.16 (Apr 2018)
- fallocate: implement zero range mode
- avoid losing data raid profile when deleting a device
- tree item checker: more checks for directory items and xattrs
- raid56 recovery: don't use cached stripes, that could be potentially changed and a later RMW or recovery would lead to corruptions or failures
- let raid56 try harder to rebuild damaged data, reading from all stripes if necessary
- fix scrub to repair raid56 in a similar way as in the case above
- cleanups: device freeing, removed some call indirections, redundant bio_put/_get, unused parameters, refactorings and renames
- RCU list traversal fixups
- simplify mount callchain, remove recursing back when mounting a subvolume
- plug for fsync, may improve bio merging on multiple devices
- compression heurisic: replace heap sort with radix sort, gains some performance
- add extent map selftests, buffered write vs dio
btrfs-progs v4.15.1 (Feb 2018)
- fix build on musl
- support asciidoctor for doc generation
- sync some code with kernel
- check: move code to own directory, split to more files
- more build tests in travis
- tests now pass with asan and ubsan
- testsuite can be exported and used separately
Read about past releases in the Changelog
Guides and usage information
- Getting started — first steps, distributions with btrfs support
- FAQ — About the btrfs project and filesystem
- UseCases — Recipes for how to do stuff with btrfs
- SysadminGuide — A more in-depth guide to btrfs's concepts and a bit of its internals, to answer all those "but what is a subvolume?" kind of questions.
- Multiple devices – A guide to the RAID features of Btrfs
- Conversion from Ext3 and Ext4 or reiserfs
- Problem FAQ — Commonly-encountered problems and solutions.
- Gotchas — lists known bugs and issues, but not necessarily solutions.
External Btrfs Documentation / Guides
Links to Btrfs documentation of various Linux distributions:
- "The Btrfs File System" chapter in the Oracle Linux 6 Administrator's Solutions Guide
- Oracle Linux Hands-on lab - Storage Management with Btrfs
- Major File Systems in Linux chapter in the SLES 11 Storage Administration Guide
- Btrfs chapter in the Red Hat Enterprise Linux 6 Storage Administration Guide
- Btrfs Wiki page on the Ubuntu Community Help Wiki
- Btrfs Wiki page on the Arch Linux Wiki
- BTRFS Fun Wiki page on the Funtoo Wiki
- Marc MERLIN's Btrfs talk at Linuxcon JP 2014 which gives an overview of Btrfs, best practices, and its more interesting features.
- Changelog — history of changes in linux kernel wrt btrfs
- Development statistics — contributors, commits, lines
- Contact information:
- Project ideas
- Cleanup ideas
- Userspace tools projects
- Manual pages generated from git (complete list):
- Original wiki documentation (obsolete, will be removed)
- restore and find-root — utilities to find and restore data from an unmountable filesystem
- Developer's FAQ — hints and answers for contributors and developers, general information about patch formatting
- Development notes — notes, hints, checklists for specific implementation tasks (eg. adding new ioctls)
- Code documentation — trees, source files, sample code for manipulating trees
- Data Structures — detailed on-disk data structures
- Trees — detailed in-tree representation of files and directories
- Btrfs design — design notes (possibly out of date in places)
- Multiple Device Support — design notes
- ENOSPC — Current ENOSPC design issues
- Design_notes_on_Send/Receive — notes from initial impelentation, protocol V2 updates draft
- Qgroups status quo - notes on some qgroups observations/pain points
- Debugging Btrfs with GDB
- Writing patch for btrfs
- Btree_Items - Mapping from Btrfs key to item-data
- Resolving_Extent_Backrefs - How back references are resolved to root owners
- Original COW B-tree: Source code in C that implements the COW B-tree algorithms repository. Written by Ohad Rodeh at IBM Research in 2006, and released under a BSD license. This is a reference implementation, that works in user space.
- Unmerged features
- In-band (write) time deduplication
- User notes on dedupe — User/tester notes for using in-band deduplication feature
- In-band (write) time deduplication
Source code download
- Btrfs source repositories
- Gitweb source viewer of the main kernel repository
- Gitweb source viewer of the userspace tools repository
The wiki contributions are welcome! Please create an account and wait for approval (this is a necessary spam protection). You can try to catch some of the wiki admins on IRC and expedite the account creation.
Articles, presentations, podcasts
- Video: NYLUG Presents: Chris Mason on Btrfs (May 14th 2015) by Chris Mason at the 192nd meeting of the NYLUG
- Video: Why you should consider using btrfs ... like Google does. by Marc Merlin at linux.conf.au 2015. talk slides
- Article: Bitrot and atomic COWs: Inside “next-gen” filesystems (ars technica, 2014/01)
- Article: Btrfs: Subvolumes and snapshots (LWN.net, 2014/01)
- Article: Btrfs: Working with multiple devices (LWN.net, 2013/12)
- Article: Btrfs: Getting started (LWN.net, 2013/12)
- Article: Btrfs hands on: An extremely cool file system (ZDNet, 2013/11)
- Technical report: Visualizating Block IO Workloads. Section six shows a visual comparison of the IO patterns for BTRFS, XFS, and EXT4. Submitted to ACM Transactions on Storage, November 2013.
- Paper: BTRFS: The Linux B-Tree Filesystem describing the overall concepts and architecture, appeared in ACM Transactions on Storage, August 2013. Includes a detailed comparison with ZFS. There is a free ACM authorized link, from O. Rodeh's  page. Otherwise, try IBM Research link
Links to old or obsolete documentation, articles. Kept for historical reasons. Stuff that's more than 3 years old.
Articles, presentations, podcasts
- Article: A Beginner's Guide To Btrfs (2012-11-26)
- Article: How I Use the Advanced Capabilities of Btrfs by Margaret Bierman with Lenz Grimmer (2012-08-11)
- Article: How I Got Started with the Btrfs File System for Oracle Linux by Margaret Bierman with Lenz Grimmer (2012-07-11)
- Video: Btrfs Filesystem: Status and New Features by Chris Mason at the 2012 Linux Foundation Collaboration Summit (2012-04-05)
- Article Btrfs - The Swiss Army Knife Of Storage by Josef Bacik (2012-02)
- Video: I Can't Believe This is Butter! A tour of btrfs by Avi Miller at linux.conf.au (2012-01-18)
- Article: A btrfs update at LinuxCon Europe on lwn.net (2011-11-02)
- Podcast: Podcast with Chris Mason: Btrfs overview and status update (2011-07-13)
- Video: The Story So Far by Josef Bacik at LinuxCon Brazil (2010-08-31)
- Article: Linux.com Weekend Project: Get Started with Btrfs (2010-10-15)
- Webcast: State of "Btrfs" File System for Linux by Chris Mason (2010-08-26) [email registration and flash required]
- Article: Valerie Aurora: A short history of btrfs (2009-07-22)
- 2012-10 BTRFS, mount options and virtual machines: an in-depth look (Ilsistemista.net)
- 2012-06 BTRFS EXT3 EXT4 XFS and KVM virtual machine: a host-side filesystem comparison (Ilsistemista.net)
- 2012-06 BTRFS vs EXT3 vs EXT4 vs XFS performance on Fedora 17 (Ilsistemista.net)
- 2012-05 Ext4, XFS and Btrfs benchmark redux
- 2011-12 Btrfs Performance Analysis
- 2011-10 EXT3 vs EXT4 vs XFS vs BTRFS - filesystems comparison on Linux kernel 3.0.0 (Ilsistemista.net)
- 2010 SSD Linux benchmarking: Comparing filesystems and encryption method
- 2010-11 EXT3 vs EXT4 vs XFS vs BTRFS linux filesystems benchmark (Ilsistemista.net)
- 2010-10 One Billion Files Btrfs performs well in comparison to other filesystems, when there are a billion files in the filesystem.
- 2008-10 Btrfs performance analysis by Steven Pratt and IBM The benchmarks from IBM demonstrate some bottlenecks we have in the extent recording on large workloads. We're working on fixes for these.