Main Page
(→Major Features Currently Implemented: link to rtd) |
m (Reverted edits by Kdave (talk) to last revision by Michal Rostecki) |
||
Line 47: | Line 47: | ||
* Dynamic inode allocation | * Dynamic inode allocation | ||
* Writable snapshots, read-only snapshots | * Writable snapshots, read-only snapshots | ||
− | * | + | * Subvolumes (separate internal filesystem roots) |
− | * | + | * Checksums on data and metadata (crc32c, xxhash, sha256, blake2b) |
* [[Compression]] (ZLIB, LZO, ZSTD), heuristics | * [[Compression]] (ZLIB, LZO, ZSTD), heuristics | ||
* Integrated [[Multiple_Device_Support|multiple device support]] | * Integrated [[Multiple_Device_Support|multiple device support]] | ||
Line 56: | Line 56: | ||
** Single and Dual Parity implementations (experimental, not production-ready) | ** 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) | * 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|incremental backup]] | ||
* Background scrub process for finding and repairing errors of files with redundant copies | * Background scrub process for finding and repairing errors of files with redundant copies | ||
− | * Online filesystem | + | * Online filesystem defragmentation |
* [[btrfsck|Offline filesystem check]] | * [[btrfsck|Offline filesystem check]] | ||
* In-place [[Conversion_from_Ext3|conversion]] of existing ext2/3/4 and reiserfs file systems | * In-place [[Conversion_from_Ext3|conversion]] of existing ext2/3/4 and reiserfs file systems | ||
* [[Seed-device|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. | * [[Seed-device|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]] | * Subvolume-aware [[quota support]] | ||
− | * | + | * Send/receive of subvolume changes |
+ | ** Efficient incremental filesystem mirroring | ||
* Batch, or out-of-band [[deduplication]] (happens after writes, not during) | * Batch, or out-of-band [[deduplication]] (happens after writes, not during) | ||
− | * | + | * Swapfile support |
* [[Tree-checker]], post-read and pre-write metadata verification | * [[Tree-checker]], post-read and pre-write metadata verification | ||
− | |||
− | |||
=== Features by kernel version === | === Features by kernel version === | ||
+ | As part of the changelog you can also review | ||
* [[Changelog#By_feature|features by kernel version]] | * [[Changelog#By_feature|features by kernel version]] | ||
Line 75: | Line 76: | ||
=== Features Currently in Development or Planned for Future Implementation === | === Features Currently in Development or Planned for Future Implementation === | ||
+ | * SMR (zoned block device) support | ||
* DAX/persistent memory support | * DAX/persistent memory support | ||
* The file/directory -level encryption support (fscrypt) | * The file/directory -level encryption support (fscrypt) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
<!-- Documentation Block --> | <!-- Documentation Block --> | ||
<div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#fffff0; align:right; "> | <div style="margin:0; margin-top:10px; margin-right:10px; border:1px solid #dfdfdf; padding:0 1em 1em 1em; background-color:#fffff0; align:right; "> | ||
− | |||
== Documentation == | == Documentation == | ||
Line 106: | Line 102: | ||
* "[https://docs.oracle.com/cd/E37670_01/E37355/html/ol_btrfs.html The Btrfs File System]" chapter in the [https://docs.oracle.com/cd/E37670_01/E37355/html/index.html Oracle Linux 6 Administrator's Solutions Guide] | * "[https://docs.oracle.com/cd/E37670_01/E37355/html/ol_btrfs.html The Btrfs File System]" chapter in the [https://docs.oracle.com/cd/E37670_01/E37355/html/index.html Oracle Linux 6 Administrator's Solutions Guide] | ||
+ | * Oracle Linux [https://wikis.oracle.com/display/oraclelinux/Hands-on+lab+-+Storage+Management+with+Btrfs Hands-on lab - Storage Management with Btrfs] | ||
* [https://documentation.suse.com/sles/15-GA/single-html/SLES-storage/#sec-filesystems-major-btrfs Major File Systems in Linux] chapter in the [https://documentation.suse.com/en-us/sles/15-GA/single-html/SLES-storage/ SLES 15 Storage Administration Guide] | * [https://documentation.suse.com/sles/15-GA/single-html/SLES-storage/#sec-filesystems-major-btrfs Major File Systems in Linux] chapter in the [https://documentation.suse.com/en-us/sles/15-GA/single-html/SLES-storage/ SLES 15 Storage Administration Guide] | ||
+ | * [https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-btrfs.html Btrfs] chapter in the [https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ Red Hat Enterprise Linux 6 Storage Administration Guide] | ||
* [https://help.ubuntu.com/community/btrfs Btrfs Wiki page] on the [https://help.ubuntu.com/community Ubuntu Community Help Wiki] | * [https://help.ubuntu.com/community/btrfs Btrfs Wiki page] on the [https://help.ubuntu.com/community Ubuntu Community Help Wiki] | ||
* [https://wiki.archlinux.org/index.php/Btrfs Btrfs Wiki page] on the [https://wiki.archlinux.org/ Arch Linux Wiki] | * [https://wiki.archlinux.org/index.php/Btrfs Btrfs Wiki page] on the [https://wiki.archlinux.org/ Arch Linux Wiki] | ||
+ | * [http://www.funtoo.org/BTRFS_Fun BTRFS Fun Wiki page] on the [http://www.funtoo.org/ Funtoo Wiki] | ||
* [http://marc.merlins.org/perso/btrfs/post_2014-05-21_My-Btrfs-Talk-at-Linuxcon-JP-2014.html Marc MERLIN's Btrfs talk at Linuxcon JP 2014] which gives an overview of Btrfs, best practices, and its more interesting features. | * [http://marc.merlins.org/perso/btrfs/post_2014-05-21_My-Btrfs-Talk-at-Linuxcon-JP-2014.html Marc MERLIN's Btrfs talk at Linuxcon JP 2014] which gives an overview of Btrfs, best practices, and its more interesting features. | ||
=== Manual pages === | === Manual pages === | ||
− | * Manual pages generated from git ([ | + | * Manual pages generated from git ([[:Category:Manpage|complete list]]): |
− | ** [ | + | ** [[Manpage/btrfs|btrfs]] — main administration tool |
− | ** [ | + | ** [[Manpage/mkfs.btrfs|mkfs.btrfs]] — creating the filesystem |
− | ** [ | + | ** [[Manpage/btrfs-check|btrfs check]] — repairing file systems |
− | ** [ | + | ** [[Manpage/btrfs-convert|btrfs-convert]] — tool to convert in-place from ext2/3/4 filesystems to btrfs. For a greater detail of how the algorithm works, please see the [[Conversion from Ext3]] page. |
* Original wiki documentation (obsolete, will be removed) | * Original wiki documentation (obsolete, will be removed) | ||
Line 158: | Line 157: | ||
== News == | == News == | ||
− | ''' | + | ''' btrfs-progs v5.10.1 (Feb 2021) ''' |
− | + | * static build works again | |
+ | * libmount 2.24+ required, not available on Cent OS 7 and the like (fix planned) | ||
− | ''' | + | ''' btrfs-progs v5.10 (Jan 2021) ''' |
− | + | * scrub status: | |
− | + | ** print percentage of progress | |
− | + | ** add size unit options | |
− | * | + | * fi usage: also print free space from statfs |
− | * fi | + | * convert: copy full 64 bit timestamp from ext4 if availalble |
− | * | + | * check: |
− | * | + | ** add ability to repair extent item generation |
− | * | + | ** new option to remove leftovers from inode number cache (-o inode_cache) |
− | * | + | * check for already running exclusive operation (balance, device add/...) when starting one |
− | ** | + | * preliminary json output support for 'device stats' |
− | * | + | * fixes: |
− | + | ** subvolume set-default: id 0 correctly falls back to toplevel | |
− | + | ** receive: align internal buffer to allow fast CRC calculation | |
− | + | ** logical-resolve: distinguish -o subvol and bind mounts | |
− | + | * build: new dependency libmount | |
− | + | * other | |
− | + | ** doc fixes and updates | |
− | + | ** new tests | |
− | + | ** ci on gitlab temporarily disabled | |
− | + | ** debugging output enhancements | |
− | * | + | |
− | + | ||
− | * | + | |
− | + | ||
− | + | ||
− | * | + | |
− | ** | + | |
− | ** | + | |
− | * | + | |
− | * | + | |
− | ** | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | ''' linux v5.10 (Dec 2020) ''' | ||
+ | * hilights | ||
+ | ** performance improvements in fsync (dbench workload: higher throughput, lower latency) | ||
+ | ** sysfs exports current exclusive operataion (balance, resize, device add/del/...) | ||
+ | ** sysfs exports supported send stream version | ||
+ | * core | ||
+ | ** direct io uses iomap infrastructure (no more ''struct buffer_head'') | ||
+ | ** space reservations for data now use ticket infrastructure | ||
+ | ** cleanups, refactoring, preparatory work | ||
+ | ** error handling improvements | ||
+ | ** fixes | ||
</div> | </div> | ||
<!-- Changelog Block --> | <!-- Changelog Block --> | ||
<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#dfefdf; align:left; margin-top:10px"> | <div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#dfefdf; align:left; margin-top:10px"> | ||
− | |||
== Changelog == | == Changelog == | ||
Line 277: | Line 272: | ||
* Contact information: | * Contact information: | ||
** [[Btrfs mailing list]] | ** [[Btrfs mailing list]] | ||
− | ** [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] on | + | ** [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] on freenode.net in the channel [irc://irc.freenode.net:6667/btrfs #btrfs] |
** Reporting bugs: | ** Reporting bugs: | ||
*** for kernel code see [[Problem_FAQ#How_do_I_report_bugs_and_issues.3F | the Bugzilla FAQ]], quick tip: use product ''File System'' and component ''btrfs''. | *** for kernel code see [[Problem_FAQ#How_do_I_report_bugs_and_issues.3F | the Bugzilla FAQ]], quick tip: use product ''File System'' and component ''btrfs''. | ||
Line 289: | Line 284: | ||
<!-- Wiki Block --> | <!-- Wiki Block --> | ||
<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#dfefdf; align:left; margin-top:10px"> | <div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#dfefdf; align:left; margin-top:10px"> | ||
− | |||
== Wiki accounts, editing == | == Wiki accounts, editing == | ||
Revision as of 12:17, 13 January 2022
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. Its main features and benefits are:
- Snapshots which do not make the full copy of files
- RAID - support for software-based RAID 0, RAID 1, RAID 10
- Self-healing - checksums for data and metadata, automatic detection of silent data corruptions
Development of Btrfs started in 2007. Since that time, Btrfs is a part of the Linux kernel and is under active development.
Jointly developed at multiple companies, Btrfs is licensed under the GPL and open for contribution from anyone.
Development and Issue ReportingFor feature status, please refer to the Status page. The Btrfs code base is stable. However, new features are still under development. Every effort is made to ensure that it remains stable and fast at 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. 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. FeaturesLinux 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
Features by kernel versionAs part of the changelog you can also review Features Currently in Development or Planned for Future Implementation
DocumentationGuides and usage information
External Btrfs Documentation / GuidesLinks to Btrfs documentation of various Linux distributions:
Manual pages
Developer documentation
|
Newsbtrfs-progs v5.10.1 (Feb 2021)
btrfs-progs v5.10 (Jan 2021)
linux v5.10 (Dec 2020)
ChangelogRead about past releases in the separate Changelog page Source code downloadBtrfs source repositories describes purpose and contents, here are a few quick links:
Articles, presentations, podcasts
Historical resourcesLinks to old or obsolete documentation, articles. Kept for historical reasons. Stuff that's more than 3 years old. Articles, presentations, podcasts
Project information/Contact
Wiki accounts, editingThe wiki contributions are welcome! Please create an account and wait for approval (this is a necessary spam protection and we cannot remove it). You can try to catch some of the wiki admins on IRC (or ping user 'kdave' in a query) to expedite the account creation. The registration requires full name for account but it's not mandatory from our perspective. The wiki User and User talk pages are created automatically but removed after account is approved. If you want to use the pages, create them manually, they won't be deleted. |