Where the well-tested raid1 profile supports two copies on N devices, raid1c3 supports three copies, and raid1c4 supports four. These new profiles have enhanced data redundancy. Additionally, with these releases raid1c3 and raid1c4 profiles have finally been introduced. xxHash, SHA256, and BLAKE2 are supported with kernel+btrfs-progs newer than these. Linux ≥ 5.5 and btrfs-progs ≥ 5.4 finally bring support for checksum algorithms that are stronger than CRC32C. It appears that ChromeOS has been using btrfs since version 69 (, "Using LXD on Your Chromebook").įacebook has "now deployed on millions of servers, driving significant efficiency gains", because "btrfs helped eliminate priority inversions caused by the journaling behavior of the previous filesystem, when used for I/O control with cgroup2", and "btrfs is the only filesystem implementation that currently works with resource isolation" (Facebook open-sources new suite of Linux kernel components and tools, code.fb.com, ). "Google is evaluating btrfs for its potential use in android, but currently the lack of native file-based encryption unfortunately makes it a nonstarter" (Filip Bystricky, linux-btrfs, ). ![]() Btrfs has been part of the mainline Linux kernel since 2.6.29, and Debian's Btrfs support was introduced in DebianSqueeze.Įxt2/3/4 filesystems are upgradeable to Btrfs however, upstream recommends backing up the data, creating a pristine btrfs filesystem with wipefs -a and mkfs.btrfs, and restoring from backup - or replicating the existing data (eg: using tar, cpio, rsync etc).ītrfs single, DUP, and raid1 profiles have been reliable since Linux 4.4, so long as the #Recommendations are observed and the pitfalls documented here are avoided (TODO: Refactor this document to make it easier to become appraised of the pitfalls and corner cases).
0 Comments
Leave a Reply. |