Main Page

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(News: progs 4.2.3)
(News: 4.3)
Line 53: Line 53:
== News ==
== News ==
'''Linux v4.3 (Nov 2015)'''
'''btrfs-progs 4.2.3 (Oct 2015)'''
'''btrfs-progs 4.2.3 (Oct 2015)'''
Line 59: Line 61:
* convert: better error message in case the filesystem is not finalized
* convert: better error message in case the filesystem is not finalized
* restore: off-by-one symlink path check fix
* restore: off-by-one symlink path check fix
'''Linux v4.2 (Aug 2015)'''
* enhancements
** transaction abort now reports the caller, not the helper function
** INO_LOOKUP ioctl: unprivileged if used to just get the rootid (aka. subvolume id)
** unified ''subvol='' and ''subvolid='' mounting, show the mounted subvol in mount options; also, ''/proc/self/mountinfo'' now always correctly shows the mounted subvolume
** reworked internal qgroup logic
** send: use received_uuid of parent during send
** sysfs: preparatory works for exporting more stats about devices
** deduplication on the same inode works
** deduplication does not change mtime/ctime
* fixes:
** in send: cloning, renames, orphans,
** few more ENOSPC fixes in case of block group creation/removal
** fix hang during inode eviction due to concurrent readahead
** EXTENT_SAME ioctl: handle unaligned length
** more fixes around automatic block group removal
** deadlock with EXTENT_SAME and readahead
** for feature NO_HOLES: fsync, truncate
'''In coreutils 8.24'''
'''In coreutils 8.24'''

Revision as of 22:46, 2 November 2015

Btrfs is a new copy on write (CoW) filesystem for Linux aimed at implementing advanced features while 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.


Stability status

The filesystem disk format is no longer unstable, and it's not expected to change unless there are strong reasons to do so. If there is a format change, file systems with a unchanged format will continue to be mountable and usable by newer kernels.

The Btrfs code base is under heavy development. Every effort is being made to keep it stable and fast. Due to the fast development speed, the state of development of the filesystem improves noticeably with every new Linux version, so it's recommended to run the most modern kernel possible.

For benchmarks, it's recommended to test the latest stable Linux version, and not any older. If possible, it's also recommendable to test the latest Linux development version. Also, it's recommended to test the different options, f.e. different compression options.

Newly added features may need a few releases to stabilize.

If you have any bug, problems, performance issues or questions while using Btrfs, please email the Btrfs mailing list (no subscription required). Please report bugs also 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.

The main Btrfs features available at the moment include:

  • 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 and LZO)
  • Integrated multiple device support
    • File Striping, File Mirroring, File Striping+Mirroring, Striping with Single and Dual Parity implementations
  • 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 fixing errors on files with redundant copies
  • Online filesystem defragmentation
  • Offline filesystem check
  • In-place conversion of existing ext3/4 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)

Additional features in development, or planned, include:

  • Fast offline filesystem check
  • Online filesystem check
  • Object-level mirroring and striping
  • Alternative checksum algorithms
  • In-band deduplication (happens during writes)
  • Other compression methods (snappy, LZ4)
  • Hot data tracking and moving to faster devices (currently being pushed as a generic feature available through VFS)


Linux v4.3 (Nov 2015)

btrfs-progs 4.2.3 (Oct 2015)

  • subvol sync: make it actually work again: it's been broken since 4.1.2, due to a reversed condition it returned immediatelly instead of waiting for
  • scanning: do not scan already discovered filesystems (minor optimization)
  • convert: better error message in case the filesystem is not finalized
  • restore: off-by-one symlink path check fix

In coreutils 8.24

  • mv will attempt reflink before falling back to standard copy [1] (release notes)

Read about past releases in the Changelog


Guides and usage information

External Btrfs Documentation / Guides

Links to Btrfs documentation of various Linux distributions:

Project information/Contact

Using the built-in tools

  • Original wiki documenation (obsolete, will be removed)

Developer documentation

  • Developer's FAQ — hints and answers for contributors and developers
  • 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

Source code download

Articles, presentations, podcasts


Historical resources

Links to old or obsolete documentation, articles. Kept for historical reasons. Stuff that's more than 3 years old.

Articles, presentations, podcasts


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.
Personal tools