Main Page

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(Features Currently in Development or Planned for Future Implementation)
(News and Changelog: progs 4.15.1)
Line 65: Line 65:
== News and Changelog ==
== News and Changelog ==
''' btrfs-progs v4.15 (Jan 2018) '''
''' btrfs-progs v4.15.1 (Feb 2018) '''
* mkfs --rootdir reworked, does not minimize the final image but can be still done using a new option --shrink
* build
* fix allocation of system chunk, don't allocate from the reserved area
** fix build on musl
* other
** support asciidoctor for doc generation
** new and updated tests
* cleanups
** cleanups, refactoring
** sync some code with kernel
** doc updates
** check: move code to own directory, split to more files
* tests
** more build tests in travis
** tests now pass with asan and ubsan
** testsuite can be exported and used separately
''' Linux v4.15 (Jan 2018) '''
''' Linux v4.15 (Jan 2018) '''

Revision as of 16:13, 16 February 2018

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.


Stability status

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 (currently being pushed as a generic feature available through VFS)
  • SMR support
  • DAX/persistent memory support
  • The file/directory -level encryption support (fscrypt)

News and Changelog

btrfs-progs v4.15.1 (Feb 2018)

  • build
    • fix build on musl
    • support asciidoctor for doc generation
  • cleanups
    • sync some code with kernel
    • check: move code to own directory, split to more files
  • tests
    • more build tests in travis
    • tests now pass with asan and ubsan
    • testsuite can be exported and used separately

Linux v4.15 (Jan 2018)

  • new features
    • extend mount options to specify zlib compression level, -o compress=zlib:9
    • v2 of ioctl "extent to inode mapping"
    • populate compression heuristics logic
    • enable indexing for btrfs as lower filesystem in overlayfs
    • speedup page cache readahead during send on large files
  • internal changes
    • more sanity checks of b-tree items when reading them from disk
    • more EINVAL/EUCLEAN fixups, missing BLK_STS_* conversion, other errno or error handling fixes
    • remove some homegrown IO-related logic, that's been obsoleted by core block layer changes (batching, plug/unplug, own counters)
    • add ref-verify, optional debugging feature to verify extent reference accounting
    • simplify code handling outstanding extents, make it more clear where and how the accounting is done
    • make delalloc reservations per-inode, simplify the code and make the logic more straightforward
    • extensive cleanup of delayed refs code
  • fix send ioctl on 32bit with 64bit kernel

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

Manual pages

  • Original wiki documentation (obsolete, will be removed)

Developer documentation

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

Source code download

Wiki editing

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

Historical resources

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

Articles, presentations, podcasts


Personal tools