|Developer(s)||Facebook, Fujitsu, Fusion-IO, Intel, Linux Foundation, Netgear, Oracle Corporation, Red Hat, STRATO AG, and SUSE|
|Full name||B-tree file system|
|Introduced||Linux kernel 2.6.29, March 2009|
|Max. volume size||16 EiB[a]|
|Max. file size||16 EiB[a]|
|Max. number of files||264[b]|
|Max. filename length||255 ASCII characters (fewer for multibyte character encodings such as Unicode)|
|Allowed characters in filenames||All except |
|Dates recorded||Creation (otime), modification (mtime), attribute modification (ctime), and access (atime)|
|Date range||64 bit signed int offset from 1970-01-01T00:00:00Z|
|Attributes||POSIX and extended attributes|
|File system permissions||POSIX and ACL|
|Transparent compression||Yes (zlib, LZO and (since 4.14) ZSTD)|
|Supported operating systems||Linux, ReactOS|
Btrfs, an abbreviation for b-tree file system, (pronounced as "butter fuss", "better F S", "butter F S", "b-tree F S", or simply by spelling it out) is a file system based on the copy-on-write (COW) principle, initially designed at Oracle Corporation for use in Linux. The development of Btrfs began in 2007, and since November 2013 the file system's on-disk format has been declared stable in the Linux kernel.
Btrfs is intended to address the lack of pooling, snapshots, checksums, and integral multi-device spanning in Linux file systems. Chris Mason, the principal Btrfs author, has stated that its goal was "to let Linux scale for the storage that will be available. Scaling is not just about addressing the storage but also means being able to administer and to manage it with a clean interface that lets people see what's being used and makes it more reliable".
- 1 History
- 2 Features
- 2.1 Implemented
- 2.2 Implemented but not recommended for production use
- 2.3 Planned but not yet implemented
- 2.4 Cloning
- 2.5 Subvolumes and snapshots
- 2.6 Send–receive
- 2.7 Quota groups
- 2.8 In-place conversion from ext2/3/4 and reiserfs
- 2.9 Union mounting / seed devices
- 2.10 Encryption
- 2.11 Checking and recovery
- 3 Design
- 4 Commercial support
- 5 See also
- 6 Notes
- 7 References
- 8 External links
The core data structure of Btrfs—the copy-on-write B-tree—was originally proposed by IBM researcher Ohad Rodeh at a presentation at USENIX 2007. Chris Mason, an engineer working on ReiserFS for SUSE at the time, joined Oracle later that year and began work on a new file system based on these B-trees.
In 2008, the principal developer of the ext3 and ext4 file systems, Theodore Ts'o, stated that although ext4 has improved features, it is not a major advance; it uses old technology and is a stop-gap. Ts'o said that Btrfs is the better direction because "it offers improvements in scalability, reliability, and ease of management". Btrfs also has "a number of the same design ideas that reiser3/4 had".
Btrfs 1.0, with finalized on-disk format, was originally slated for a late-2008 release, and was finally accepted into the Linux kernel mainline in 2009. Several Linux distributions began offering Btrfs as an experimental choice of root file system during installation.
In July 2011, Btrfs automatic defragmentation and scrubbing features were merged into version 3.0 of the Linux kernel mainline. Besides Mason at Oracle, Miao Xie at Fujitsu contributed performance improvements. In June 2012, Chris Mason left Oracle for Fusion-io, which he left a year later with Josef Bacik to join Facebook; while at both companies, Mason continued his work on Btrfs.
In August 2017, Red Hat announced in the release notes for Red Hat Enterprise Linux (RHEL) 7.4 that it no longer planned to move Btrfs, which had been included as a "technology preview" since RHEL 6 beta, to a fully supported feature, noting that it would remain available in the RHEL 7 release series. Btrfs was removed from RHEL 8 in May 2019.
- Mostly self-healing in some configurations due to the nature of copy-on-write
- Online defragmentation and an autodefrag mount option
- Online volume growth and shrinking
- Online block device addition and removal
- Online balancing (movement of objects between block devices to balance load)
- Offline filesystem check
- Online data scrubbing for finding errors and automatically fixing them for files with redundant copies
- RAID 0, RAID 1, and RAID 10
- Subvolumes (one or more separately mountable filesystem roots within each disk partition)
- Transparent compression via zlib, LZO and (since 4.14) ZSTD, configurable per file or volume
- Atomic writable (via copy-on-write) or read-only Snapshots of subvolumes
- File cloning (copy-on-write on individual files) via
cp --reflink <source file> <destination file>
- Checksums on data and metadata (CRC-32C)
- In-place conversion from ext3/4 to Btrfs (with rollback). This feature regressed around btrfs-progs version 4.0, rewritten from scratch in 4.6.
- Union mounting of read-only storage, known as file system seeding (read-only storage used as a copy-on-write backing for a writable Btrfs)
- Block discard (reclaims space on some virtualized setups and improves wear leveling on SSDs with TRIM)
- Send/receive (saving diffs between snapshots to a binary stream)
- Incremental backup
- Out-of-band data deduplication (requires userspace tools)
- Ability to handle swap files and swap partitions
Implemented but not recommended for production use
Planned but not yet implemented
- In-band data deduplication
- Online filesystem check
- RAID with up to six parity devices, surpassing the reliability of RAID 5 and RAID 6
- Object-level RAID 0, RAID 1, and RAID 10
In 2009, Btrfs was expected to offer a feature set comparable to ZFS, developed by Sun Microsystems. After Oracle's acquisition of Sun in 2009, Mason and Oracle decided to continue with Btrfs development.
Btrfs provides a clone operation that atomically creates a copy-on-write snapshot of a file. Such cloned files are sometimes referred to as reflinks, in light of the associated Linux kernel system calls.
By cloning, the file system does not create a new link pointing to an existing inode; instead, it creates a new inode that initially shares the same disk blocks with the original file. As a result, cloning works only within the boundaries of the same Btrfs file system, but since version 3.6 of the Linux kernel it may cross the boundaries of subvolumes under certain circumstances. The actual data blocks are not duplicated; at the same time, due to the copy-on-write (CoW) nature of Btrfs, modifications to any of the cloned files are not visible in the original file and vice versa.
Cloning should not be confused with hard links, which are directory entries that associate multiple file names with actual files on a file system. While hard links can be taken as different names for the same file, cloning in Btrfs provides independent files that initially share all their disk blocks.
Subvolumes and snapshots
A Btrfs subvolume can be thought of as a separate POSIX file namespace, mountable separately by passing
subvolid options to the utility. It can also be accessed by mounting the top-level subvolume, in which case subvolumes are visible and accessible as its subdirectories.
Subvolumes can be created at any place within the file system hierarchy, and they can also be nested. Nested subvolumes appear as subdirectories within their parent subvolumes, similarly to the way a top-level subvolume presents its subvolumes as subdirectories. Deleting a subvolume is not possible until all subvolumes below it in the nesting hierarchy are deleted; as a result, top-level subvolumes cannot be deleted.
Any Btrfs file system always has a default subvolume, which is initially set to be the top-level subvolume, and is mounted by default if no subvolume selection option is passed to
mount. The default subvolume can be changed as required.
A Btrfs snapshot is a subvolume that shares its data (and metadata) with some other subvolume, using Btrfs' copy-on-write capabilities, and modifications to a snapshot are not visible in the original subvolume. Once a writable snapshot is made, it can be treated as an alternate version of the original file system. For example, to roll back to a snapshot, a modified original subvolume needs to be unmounted and the snapshot needs to be mounted in its place. At that point, the original subvolume may also be deleted.
The copy-on-write (CoW) nature of Btrfs means that snapshots are quickly created, while initially consuming very little disk space. Since a snapshot is a subvolume, creating nested snapshots is also possible. Taking snapshots of a subvolume is not a recursive process; thus, if a snapshot of a subvolume is created, every subvolume or snapshot that the subvolume already contains is mapped to an empty directory of the same name inside the snapshot.
Taking snapshots of a directory is not possible, as only subvolumes can have snapshots. However, there is a workaround that involves reflinks spread across subvolumes: a new subvolume is created, containing cross-subvolume reflinks to the content of the targeted directory. Having that available, a snapshot of this new volume can be created.
A subvolume in Btrfs is quite different from a traditional Logical Volume Manager (LVM) logical volume. With LVM, a logical volume is a separate block device, while a Btrfs subvolume is not and it cannot be treated or used that way. Making dd or LVM snapshots of btrfs leads to dataloss if either the original or the copy is mounted while both are on the same computer.
Given any pair of subvolumes (or snapshots), Btrfs can generate a binary diff between them (by using the
btrfs send command) that can be replayed later (by using
btrfs receive), possibly on a different Btrfs file system. The send–receive feature effectively creates (and applies) a set of data modifications required for converting one subvolume into another.
The send/receive feature can be used with regularly scheduled snapshots for implementing a simple form of file system master–slave replication, or for the purpose of performing incremental backups.
A quota group (or qgroup) imposes an upper limit to the space a subvolume or snapshot may consume. A new snapshot initially consumes no quota because its data is shared with its parent, but thereafter incurs a charge for new files and copy-on-write operations on existing files. When quotas are active, a quota group is automatically created with each new subvolume or snapshot. These initial quota groups are building blocks which can be grouped (with the
btrfs qgroup command) into hierarchies to implement quota pools.
Quota groups only apply to subvolumes and snapshots, while having quotas enforced on individual subdirectories, users, or user groups is not possible. However, workarounds are possible by using different subvolumes for all users or user groups that require a quota to be enforced.
In-place conversion from ext2/3/4 and reiserfs
As the result of having very little metadata anchored in fixed locations, Btrfs can warp to fit unusual spatial layouts of the backend storage devices. The
btrfs-convert tool exploits this ability to do an in-place conversion of an ext2/3/4 or ReiserFS file system, by nesting the equivalent Btrfs metadata in its unallocated space—while preserving an unmodified copy of the original file system.
The conversion involves creating a copy of the whole ext2/3/4 metadata, while the Btrfs files simply point to the same blocks used by the ext2/3/4 files. This makes the bulk of the blocks shared between the two filesystems before the conversion becomes permanent. Thanks to the copy-on-write nature of Btrfs, the original versions of the file data blocks are preserved during all file modifications. Until the conversion becomes permanent, only the blocks that were marked as free in ext2/3/4 are used to hold new Btrfs modifications, meaning that the conversion can be undone at any time (although doing so will erase any changes made after the conversion to Btrfs).
All converted files are available and writable in the default subvolume of the Btrfs. A sparse file holding all of the references to the original ext2/3/4 filesystem is created in a separate subvolume, which is mountable on its own as a read-only disk image, allowing both original and converted file systems to be accessed at the same time. Deleting this sparse file frees up the space and makes the conversion permanent.
As of June 2015 and 4.x versions of the Linux kernel mainline, the in-place ext3/4 conversion was considered untested and rarely used. The feature, however, was rewritten from scratch in 2016 for
btrfs-progs 4.6. and is considered stable since then.
In-place conversion from ReiserFS was introduced in September 2017 with kernel 4.13.
Union mounting / seed devices
When creating a new Btrfs, an existing Btrfs can be used as a read-only "seed" file system. The new file system will then act as a copy-on-write overlay on the seed, as a form of union mounting. The seed can be later detached from the Btrfs, at which point the rebalancer will simply copy over any seed data still referenced by the new file system before detaching. Mason has suggested this may be useful for a Live CD installer, which might boot from a read-only Btrfs seed on an optical disc, rebalance itself to the target partition on the install disk in the background while the user continues to work, then eject the disc to complete the installation without rebooting.
In his 2009 interview, Chris Mason stated that support for encryption was planned for Btrfs. In the meantime, a workaround for combining encryption with Btrfs is to use a full-disk encryption mechanism such as dm-crypt / LUKS on the underlying devices and to create the Btrfs filesystem on top of that layer.
Checking and recovery
This section's factual accuracy may be compromised due to out-of-date information. (November 2016)
Unix systems traditionally rely on "fsck" programs to check and repair filesystems. This functionality is implemented via the
btrfs check program. Since version 4.0 this functionality is deemed relatively stable. However, as of August 2017, the btrfs documentation suggests that it be used only after having tried other recovery methods.
There is another tool, named
btrfs-restore, that can be used to recover files from an unmountable filesystem, without modifying the broken filesystem itself (i.e., non-destructively).
In normal use, Btrfs is mostly self-healing and can recover from broken root trees at mount time, thanks to making periodic data flushes to permanent storage, by default every 30 seconds. Thus, isolated errors will cause a maximum of 30 seconds of filesystem changes to be lost at the next mount. This period can be changed by specifying a desired value (in seconds) for the
commit mount option.
Ohad Rodeh's original proposal at USENIX 2007 noted that B+ trees, which are widely used as on-disk data structures for databases, could not efficiently allow copy-on-write-based snapshots because its leaf nodes were linked together: if a leaf was copy-on-written, its siblings and parents would have to be as well, as would their siblings and parents and so on until the entire tree was copied. He suggested instead a modified B-tree (which has no leaf linkage), with a refcount associated to each tree node but stored in an ad-hoc free map structure and certain relaxations to the tree's balancing algorithms to make them copy-on-write friendly. The result would be a data structure suitable for a high-performance object store that could perform copy-on-write snapshots, while maintaining good concurrency.
At Oracle later that year, Chris Mason began work on a snapshot-capable file system that would use this data structure almost exclusively—not just for metadata and file data, but also recursively to track space allocation of the trees themselves. This allowed all traversal and modifications to be funneled through a single code path, against which features such as copy-on-write, checksumming and mirroring needed to be implemented only once to benefit the entire file system.
Btrfs is structured as several layers of such trees, all using the same B-tree implementation. The trees store generic items sorted on a 136-bit key. The first 64 bits of the key are a unique object id. The middle 8 bits are an item type field; its use is hardwired into code as an item filter in tree lookups. Objects can have multiple items of multiple types. The remaining right-hand 64 bits are used in type-specific ways. Therefore, items for the same object end up adjacent to each other in the tree, ordered by type. By choosing certain right-hand key values, objects can further put items of the same type in a particular order.
Interior tree nodes are simply flat lists of key-pointer pairs, where the pointer is the logical block number of a child node. Leaf nodes contain item keys packed into the front of the node and item data packed into the end, with the two growing toward each other as the leaf fills up.
This section does not cite any sources. (January 2017) (Learn how and when to remove this template message)
Every tree appears as an object in the root tree (or tree of tree roots). Some trees, such as file system trees and log trees, have a variable number of instances, each of which is given its own object id. Trees which are singletons (the data relocation, extent and chunk trees) are assigned special, fixed object ids ≤255. The root tree appears in itself as a tree with object id 1.
Trees refer to each other by object id. They may also refer to individual nodes in other trees as a triplet of the tree's object id, the node's level within the tree and its leftmost key value. Such references are independent of where the tree is actually stored.
File system tree
User-visible files and directories are contained in a file system tree. There is one file system tree per subvolume. Subvolumes can nest, in which case they appear as a directory item (described below) whose data is a reference to the nested subvolume's file system tree.
Within each directory, directory entries appear as directory items, whose right-hand key values are a CRC32C hash of their filename. Their data is a location key, or the key of the inode item it points to. Directory items together can thus act as an index for path-to-inode lookups, but are not used for iteration because they are sorted by their hash, effectively randomly permuting them. This means user applications iterating over and opening files in a large directory would thus generate many more disk seeks between non-adjacent files—a notable performance drain in other file systems with hash-ordered directories such as ReiserFS, ext3 (with Htree-indexes enabled) and ext4, all of which have TEA-hashed filenames. To avoid this, each directory entry has a directory index item, whose right-hand key value of the item is set to a per-directory counter that increments with each new directory entry. Iteration over these index items thus returns entries in roughly the same order as they are stored on disk.
Besides inode items, files and directories also have a reference item whose right-hand key value is the object id of their parent directory. The data part of the reference item is the filename that inode is known by in that directory. This allows upward traversal through the directory hierarchy by providing a way to map inodes back to paths.
Files with hard links in multiple directories have multiple reference items, one for each parent directory. Files with multiple hard links in the same directory pack all of the links' filenames into the same reference item. This was a design flaw that limited the number of same-directory hard links to however many could fit in a single tree block. (On the default block size of 4 KiB, an average filename length of 8 bytes and a per-filename header of 4 bytes, this would be less than 350.) Applications which made heavy use of multiple same-directory hard links, such as git, GNUS, GMame and BackupPC were later observed to fail after hitting this limit. The limit was eventually removed (and as of October 2012 has been merged pending release in Linux 3.7) by introducing spillover extended reference items to hold hard link filenames which could not otherwise fit.
This section needs additional citations for verification. (January 2017) (Learn how and when to remove this template message)
File data is kept outside the tree in extents, which are contiguous runs of disk blocks. Extent blocks default to 4KiB in size, do not have headers and contain only (possibly compressed) file data. In compressed extents, individual blocks are not compressed separately; rather, the compression stream spans the entire extent.
Files have extent data items to track the extents which hold their contents. The item's right-hand key value is the starting byte offset of the extent. This makes for efficient seeks in large files with many extents, because the correct extent for any given file offset can be computed with just one tree lookup.
Snapshots and cloned files share extents. When a small part of a large such extent is overwritten, the resulting copy-on-write may create three new extents: a small one containing the overwritten data, and two large ones with unmodified data on either side of the overwrite. To avoid having to re-write unmodified data, the copy-on-write may instead create bookend extents, or extents which are simply slices of existing extents. Extent data items allow for this by including an offset into the extent they are tracking: items for bookends are those with non-zero offsets.
If the file data is small enough to fit inside a tree node, it is instead pulled in-tree and stored inline in the extent data item. Each tree node is stored in its own tree block—a single uncompressed block with a header. The tree block is regarded as a free-standing, single-block extent.
Extent allocation tree
This section needs additional citations for verification. (January 2017) (Learn how and when to remove this template message)
The extent allocation tree acts as an allocation map for the file system. Unlike other trees, items in this tree do not have object ids and represent regions of space: their left-hand and right-hand key values are the starting offsets and lengths of the regions they represent.
The file system zones its allocated space into block groups, which are variable-sized allocation regions that alternate successively between preferring metadata extents (tree nodes) and data extents (file contents). The default ratio of data to metadata block groups is 1:2. They are intended to work like the Orlov block allocator and block groups in ext3 in allocating related files together and resisting fragmentation by leaving allocation gaps between groups. (ext3 block groups, however, have fixed locations computed from the size of the file system, whereas those in Btrfs are dynamic and are created as needed.) Each block group is associated with a block group item. Inode items in the file system tree include a reference to their current block group.
Extent items contain a back-reference to the tree node or file occupying that extent. There may be multiple back-references if the extent is shared between snapshots. If there are too many back-references to fit in the item, they spill out into individual extent data reference items. Tree nodes, in turn, have back-references to their containing trees. This makes it possible to find which extents or tree nodes are in any region of space by doing a B-tree range lookup on a pair of offsets bracketing that region, then following the back-references. For relocating data, this allows an efficient upwards traversal from the relocated blocks to quickly find and fix all downwards references to those blocks, without having to walk the entire file system. This, in turn, allows the file system to efficiently shrink, migrate and defragment its storage online.
The extent allocation tree, as with all other trees in the file system, is copy-on-write. Writes to the file system may thus cause a cascade whereby changed tree nodes and file data result in new extents being allocated, causing the extent tree to itself change. To avoid creating a feedback loop, extent tree nodes which are still in memory but not yet committed to disk may be updated in-place to reflect new copy-on-written extents.
In theory, the extent allocation tree makes a conventional free-space bitmap unnecessary because the extent allocation tree acts as a B-tree version of a BSP tree. In practice, however, an in-memory red-black tree of page-sized bitmaps is used to speed up allocations. These bitmaps are persisted to disk (starting in Linux 2.6.37, via the
space_cache mount option) as special extents that are exempt from checksumming and copy-on-write. The extent items tracking these extents are stored in the root tree.
Checksum tree and scrubbing
CRC-32C checksums are computed for both data and metadata and stored as checksum items in a checksum tree. There is room for 256 bits of metadata checksums and up to a full leaf block (roughly 4 KB or more) for data checksums. More checksum algorithm options are planned for the future.
There is one checksum item per contiguous run of allocated blocks, with per-block checksums packed end-to-end into the item data. If there are more checksums than can fit, they spill rightwards over into another checksum item in a new leaf. If the file system detects a checksum mismatch while reading a block, it first tries to obtain (or create) a good copy of this block from another device – if internal mirroring or RAID techniques are in use.
Btrfs can initiate an online check of the entire file system by triggering a file system scrub job that is performed in the background. The scrub job scans the entire file system for integrity and automatically attempts to report and repair any bad blocks it finds along the way.
An fsync is a request to commit modified data immediately to stable storage. fsync-heavy workloads (like a database or a virtual machine whose running OS fsyncs intensively) could potentially generate a great deal of redundant write I/O by forcing the file system to repeatedly copy-on-write and flush frequently modified parts of trees to storage. To avoid this, a temporary per-subvolume log tree is created to journal fsync-triggered copy-on-writes. Log trees are self-contained, tracking their own extents and keeping their own checksum items. Their items are replayed and deleted at the next full tree commit or (if there was a system crash) at the next remount.
Chunk and device trees
This section does not cite any sources. (January 2017) (Learn how and when to remove this template message)
Block devices are divided into physical chunks of 256 MB or more. Physical chunks across multiple devices can be mirrored or striped together into a single logical chunk. These logical chunks are combined into a single logical address space that the rest of the filesystem uses.
The chunk tree tracks this by storing each device therein as a device item and logical chunks as chunk map items, which provide a forward mapping from logical to physical addresses by storing their offsets in the right-hand 64 bits of their key. Chunk map items can be one of several different types:
- 1 logical to 1 physical chunk
- 1 logical chunk to 2 physical chunks on 1 block device
- N logical chunks to N≥2 physical chunks across N≥2 block devices
- 1 logical chunk to N≥2 physical chunks across N≥2 block devices
- N-1 logical chunks to N≥3 physical chunks across N≥3 block devices, with 1 physical chunk used as parity
- N-2 logical chunks to N≥4 physical chunks across N≥4 block devices, with 2 physical chunks used as parity
N is however many block devices still have free space when the chunk is allocated. If N is not large enough for the chosen mirroring/mapping, then the filesystem is effectively out of space.
The device tree is the inverse of the chunk tree, and has device extent items which provide a reverse mapping from byte-ranges of block devices back to logical chunks by storing the device number in the left hand 64-bits and physical offset in the right-hand 64 bits of they key.
These two trees together allow Btrfs to grow, shrink and even change RAID levels without unmounting because they make it possible to efficiently locate the chunks affected by shrink/move operations and then relocate their contents on-the-fly.
The file system, chunks and devices are all assigned a Universally Unique Identifier (UUID). The header of every tree node contains both the UUID of its containing chunk and the UUID of the file system. The chunk and device trees refer to devices and chunks with UUIDs. On filesystems with just a single block device, "dup" is also the default profile for metadata. All this is intended to improve the odds of successful data salvage in the event of media errors).
Defragmentation, shrinking and rebalancing operations require extents to be relocated. However, doing a simple copy-on-write of the relocating extent will break sharing between snapshots and consume disk space. To preserve sharing, an update-and-swap algorithm is used, with a special relocation tree serving as scratch space for affected metadata. The extent to be relocated is first copied to its destination. Then, by following backreferences upward through the affected subvolume's file system tree, metadata pointing to the old extent is progressively updated to point at the new one; any newly updated items are stored in the relocation tree. Once the update is complete, items in the relocation tree are swapped with their counterparts in the affected subvolume, and the relocation tree is discarded.
All the file system's trees—including the chunk tree itself—are stored in chunks, creating a potential bootstrapping problem when mounting the file system. To bootstrap into a mount, a list of physical addresses of chunks belonging to the chunk and root trees must be stored in the superblock.
Superblock mirrors are kept at fixed locations: 64 KiB into every block device, with additional copies at 64 MiB, 256 GiB and 1 PiB. When a superblock mirror is updated, its generation number is incremented. At mount time, the copy with the highest generation number is used. All superblock mirrors are updated in tandem, except in SSD mode which alternates updates among mirrors to provide some wear levelling.
- Oracle Linux 7x
- SUSE Linux Enterprise Server 15 
- Synology Inc. DiskStation Manager (DSM) v6
No longer supported
- Btrfs was included as a "technology preview" in Red Hat Enterprise Linux 6 and 7; it was removed in RHEL 8 in 2018.
- Comparison of file systems
- APFS, a copy-on-write file system for macOS, iOS, tvOS, watchOS and audioOS
- HAMMER – DragonFly BSD's file system that uses B-trees, paired with checksums as a countermeasure for data corruption
- ReFS, a copy-on-write file system for Windows Server 2012
- List of file systems
- This is the Btrfs' own on-disk size limit. The limit is reduced down to 8 EiB on 64-bit systems and 2 EiB on 32-bit systems due to Linux kernel's internal limits, unless kernel's
CONFIG_LBDconfiguration option (available since the 2.6.x kernel series) is enabled to remove these kernel limits.
- Every item in Btrfs has a 64-bit identifier, which means the most files one can have on a Btrfs filesystem is 264.
- "Btrfs Contributors at kernel.org". kernel.org. 18 January 2016. Retrieved 20 January 2016.
- "Suse Documentation: Storage Administration Guide – Large File Support in Linux". SUSE. Retrieved 12 August 2015.
- Mason, Chris. "Btrfs design". Btrfs wiki. Retrieved 8 November 2011.
- Jonathan Corbet (26 July 2010). "File creation times". LWN.net. Retrieved 15 August 2015.
- "On-disk Format - btrfs Wiki". btrfs.wiki.kernel.org.
- "btrfs Wiki". kernel.org. Retrieved 19 April 2015.
- "Linux_4.14 - Linux Kernel Newbies". kernelnewbies.org.
- McPherson, Amanda (22 June 2009). "A Conversation with Chris Mason on BTRfs: the next generation file system for Linux". Linux Foundation. Archived from the original on 27 June 2012. Retrieved 2009-09-01.
- "Deduplication". kernel.org. Retrieved 19 April 2015.
- "ReactOS 0.4.1 Released". reactos.org. Retrieved 11 August 2016.
- Henson, Valerie (31 January 2008). Chunkfs: Fast file system check and repair. Melbourne, Australia. Event occurs at 18m 49s. Retrieved 5 February 2008.
It's called Butter FS or B-tree FS, but all the cool kids say Butter FS
- "Linux kernel commit changing stability status in fs/btrfs/Kconfig". Retrieved 8 February 2019.
- Kerner, Sean Michael (30 October 2008). "A Better File System for Linux?". InternetNews.com. Archived from the original on 8 April 2011. Retrieved 30 October 2008.
- Rodeh, Ohad (2007). B-trees, shadowing, and clones (PDF). USENIX Linux Storage & Filesystem Workshop. Also Rodeh, Ohad (2008). "B-trees, shadowing, and clones". ACM Transactions on Storage.
- "Lead Btrfs File-System Developers Join Facebook". phoronix.com. Retrieved 19 April 2015.
- Paul, Ryan (13 April 2009). "Panelists ponder the kernel at Linux Collaboration Summit". Ars Technica. Archived from the original on 17 June 2012. Retrieved 2009-08-22. Cite journal requires
- Ts'o, Theodore (1 August 2008). "Re: reiser4 for 2.6.27-rc1". linux-kernel (Mailing list). Retrieved 31 December 2010.
- "Development timeline". Btrfs wiki. 11 December 2008. Archived from the original on 20 December 2008. Retrieved 5 November 2011.
- Wuelfing, Britta (12 January 2009). "Kernel 2.6.29: Corbet Says Btrfs Next Generation Filesystem". Linux Magazine. Retrieved 5 November 2011.
- "Red Hat Enterprise Linux 6 documentation: Technology Previews". Archived from the original on 28 May 2011. Retrieved 21 January 2011.
- "Fedora Weekly News Issue 276". 25 May 2011.
- "Debian 6.0 "Squeeze" released" (Press release). Debian. 6 February 2011. Retrieved 8 February 2011.
Support has also been added for the ext4 and Btrfs filesystems...
- "Linux kernel 3.0, Section 1.1. Btrfs: Automatic defragmentation, scrubbing, performance improvements". kernelnewbies.org. 21 July 2011. Retrieved 5 April 2016.
- Leemhuis, Thorsten (21 June 2011). "Kernel Log: Coming in 3.0 (Part 2) - Filesystems". The H Open. Retrieved 8 November 2011.
- Sam Varghese. "iTWire". itwire.com. Retrieved 19 April 2015.
- "Unbreakable Enterprise Kernel Release 2 has been released". Retrieved 8 May 2019.
- "SLES 11 SP2 Release Notes". 21 August 2012. Retrieved 29 August 2012.
- "SUSE Linux Enterprise Server 12 Release Notes". 5 November 2015. Retrieved 20 January 2016.
- "Red Hat Enterprise Linux 7.4 Release Notes, Chapter 53: Deprecated Functionality". 1 August 2017. Retrieved 15 August 2017.
- "Considerations in adopting RHEL 8". Product Documentation for Red Hat Enterprise Linux 8. Red Hat. Retrieved 9 May 2019.
- "Btrfs Wiki: Features". btrfs.wiki.kernel.org. 27 November 2013. Retrieved 27 November 2013.
- "Btrfs Wiki: Changelog". btrfs.wiki.kernel.org. 29 May 2019. Retrieved 27 November 2013.
- "Manpage btrfs-check".
- "Using Btrfs with Multiple Devices". kernel.org. 7 November 2013. Retrieved 20 November 2013.
- "Compression". kernel.org. 25 June 2013. Retrieved 1 April 2014.
- "Btrfs: add support for inode properties". kernel.org. 28 January 2014. Retrieved 1 April 2014.
- "btrfs: Readonly snapshots". Retrieved 12 December 2011.
- "Save disk space on Linux by cloning files on Btrfs and OCFS2". Retrieved 1 August 2017.
- "Wiki FAQ: What checksum function does Btrfs use?". Btrfs wiki. Retrieved 15 June 2009.
- "Btrfs progs release 4.6". Retrieved 1 August 2017.
- Mason, Chris (12 January 2009). "Btrfs changelog". Archived from the original on 29 February 2012. Retrieved 12 February 2012.
- Corbet, Jonathan (11 July 2012), Btrfs send/receive, LWN.net, retrieved 14 November 2012
- "Btrfs Wiki: Incremental Backup". 27 May 2013. Retrieved 27 November 2013.
- "Btrfs Wiki: Deduplication". 13 September 2013. Retrieved 27 November 2013.
- Jansen, Arne (2011), Btrfs Subvolume Quota Groups (PDF), Strato AG, retrieved 14 November 2012
- btrfs (16 July 2016). "RAID 5/6". kernel.org. Retrieved 1 October 2016.
- Corbet, Jonathan (2 November 2011). "A btrfs update at LinuxCon Europe". Retrieved 12 February 2012.
- Mazzoleni, Andrea. "btrfs: lib: raid: New RAID library supporting up to six parities". Retrieved 16 March 2014.
- "Btrfs Project ideas". 21 February 2013. Retrieved 21 February 2013.
- Aurora, Valerie (22 July 2009). "A short history of btrfs". LWN.net. Retrieved 5 November 2011.
- Hilzinger, Marcel (22 April 2009). "Future of Btrfs Secured". Linux Magazine. Retrieved 5 November 2011.
- Jonathan Corbet (5 May 2009). "The two sides of reflink()". LWN.net. Retrieved 17 October 2013.
- "UseCases – btrfs documentation". kernel.org. Retrieved 4 November 2013.
- "btrfs: allow cross-subvolume file clone". github.com. Retrieved 4 November 2013.
- "Symlinks reference names, hardlinks reference meta-data and reflinks reference data". pixelbeat.org. 27 October 2010. Retrieved 17 October 2013.
- Meyering, Jim (20 August 2009). "GNU coreutils NEWS: Noteworthy changes in release 7.5". savannah.gnu.org. Retrieved 30 August 2009.
- Scrivano, Giuseppe (1 August 2009). "cp: accept the --reflink option". savannah.gnu.org. Retrieved 2 November 2009.
- "SysadminGuide – Btrfs documentation". kernel.org. Retrieved 31 October 2013.
- "5.6 Creating Subvolumes and Snapshots [needs update]". oracle.com. 2013. Retrieved 31 October 2013.
- "Gotchas - btrfs Wiki". btrfs.wiki.kernel.org.
- "5.7 Using the Send/Receive Feature". oracle.com. 2013. Retrieved 31 October 2013.
- Mason, Chris (25 June 2015). "Conversion from Ext3 (Btrfs documentation)". kernel.org. Retrieved 22 April 2016.
- "btrfs-convert(8) manual page". Retrieved 24 April 2018.
- "Seed device".
- Mason, Chris (5 April 2012), Btrfs Filesystem: Status and New Features, Linux Foundation, retrieved 16 November 2012[permanent dead link]
- Amanda McPherson (22 June 2009). "A Conversation with Chris Mason on BTRfs: the next generation file system for Linux". Linux Foundation. Archived from the original on 27 June 2012. Retrieved 9 October 2014.
In future releases we plan to add online fsck, deduplication, encryption and other features that have been on admin wish lists for a long time.
- "Btrfsck - btrfs Wiki". btrfs.wiki.kernel.org.
- "Restore - btrfs Wiki". btrfs.wiki.kernel.org.
- "Problem FAQ - btrfs Wiki". kernel.org. 31 July 2013. Retrieved 16 January 2014.
- "kernel/git/torvalds/linux.git: Documentation: filesystems: add new btrfs mount options (Linux kernel source tree)". kernel.org. 21 November 2013. Retrieved 6 February 2014.
- "Mount options - btrfs Wiki". kernel.org. 12 November 2013. Retrieved 16 January 2014.
- Reiser, Hans (7 December 2001). "Re: Ext2 directory index: ALS paper and benchmarks". ReiserFS developers mailing list. Retrieved 28 August 2009.
- Mason, Chris. "Acp". Oracle personal web page. Retrieved 5 November 2011.
- Fasheh, Mark (9 October 2012), btrfs: extended inode refs, archived from the original on 15 April 2013, retrieved 7 November 2012
- Torvalds, Linus (10 October 2012), "Pull btrfs update from Chris Mason", git.kernel.org, archived from the original on 15 April 2013, retrieved 7 November 2012
- Larabel, Michael (24 December 2010). "Benchmarks Of The Btrfs Space Cache Option". Phoronix. Retrieved 16 November 2012.
- "FAQ - btrfs Wiki: What checksum function does Btrfs use?". The btrfs Project. Retrieved 19 September 2013.
- Bierman, Margaret; Grimmer, Lenz (August 2012). "How I Use the Advanced Capabilities of Btrfs". Retrieved 20 September 2013.
- Salter, Jim (15 January 2014). "Bitrot and atomic COWs: Inside "next-gen" filesystems". Ars Technica. Retrieved 15 January 2014.
- Coekaerts, Wim (28 September 2011). "btrfs scrub - go fix corruptions with mirror copies please!". Retrieved 20 September 2013.
- Mason, Chris; Rodeh, Ohad; Bacik, Josef (9 July 2012), BTRFS: The Linux B-tree Filesystem (PDF), IBM Research, retrieved 12 November 2012
- Mason, Chris (30 April 2008). "Multiple device support". Btrfs wiki. Archived from the original on 20 July 2011. Retrieved 5 November 2011.
- Bartell, Sean (20 April 2010). "Re: Restoring BTRFS partition". linux-btrfs (Mailing list).
- "Oracle Now Supports Btrfs RAID5/6 On Their Unbreakable Enterprise Kernel - Phoronix". www.phoronix.com.
- "SUSE reaffirms support for Btrfs [LWN.net]". lwn.net.
- "Release Notes | SUSE Linux Enterprise Server 15 GA". www.suse.com.
- "DiskStation Manager - Knowledge Base | Synology Inc". www.synology.com.
- "BionicBeaver/ReleaseNotes - Ubuntu Wiki". wiki.ubuntu.com.
- "Btrfs has been deprecated in RHEL | Hacker News". news.ycombinator.com.
- "Red Hat Appears To Be Abandoning Their Btrfs Hopes - Phoronix". www.phoronix.com.
- Andreas Jaeger (15 February 2005). "Large File Support in Linux". users.suse.com. Retrieved 12 August 2015.
- "Linux kernel configuration help for CONFIG_LBD in 2.6.29 on x86". kernel.xc.net. Archived from the original on 6 September 2015. Retrieved 12 August 2015.
- Official website
- on YouTube – a conference presentation by Avi Miller, an Oracle engineer
- Btrfs: Working with multiple devices – LWN.net, December 2013, by Jonathan Corbet
- Marc's Linux Btrfs posts – detailed insights into various Btrfs features
- Btrfs overview, LinuxCon 2014, by Marc Merlin
- File System Evangelist and Thought Leader: An Interview with Valerie Aurora, Linux Magazine, 14 July 2009, by Jeffrey B. Layton