After writing about Btrfs LZ4 compression support
and that the Btrfs FSCK tool wasn't available, it turns out that there is the new Btrfs repair tool, but it's not widely known and it's not recommended to ever use it -- at least at this stage.
As pointed out by Phoronix readers
, from the btrfs-progs Git tree
on Kernel.org is a new branch that was pushed a little more than one week ago. This new branch is called "dangerdonteveruse" (expanded: don't ever use [it]) and contains the ability to fix Btrfs file-systems.
From a Phoronix reader, "The fixing-fsck for btrfs is not missing or behind closed doors in any sense, it's just not advertised (as the only thing worse than an unmountable filesystem is a mountable filesystem with the data hopelessly garbled). That decision been completely vindicated by the number of people who come into #btrfs or posting on the mailing list about broken filesystems only after they've run btrfs-zero-log (a tool to fix one very specific problem) or btrfs-select-super (which destructively overwrites the other supers with the selected one: you get one shot)"
Over the current state of btrfs-progs proper, this "don't ever use" branch has new balance support commands for balancing chunks across drives and other RAID restriper work, a new sub-command parser, and most notably is the --repair
option. The new btrfsck --repair
option currently handles fixing errors in the extent allocation tree and block group accounting. The btrfsck
program has also picked up an --init-csum-tree
command that will replace the check-sum root with an empty one. This will clear out the CRCs but allow the Btrfs file-system to be mounted with the nodatasum
In order to test out this support, the btrfs-corrupt-block
utility in btrfs-progs has picked up an -e
option, which will corrupt the extent record by zeroing out the extent allocation tree records. There's also now a -E
option to randomly corrupt the extent_root.
The last commit to the "dangerdonteveruse" branch was on 10 February, which comes in just shy of the Valentine's Day deadline
. Btrfs is going production ready in Oracle Linux
and other Linux distributions will likely follow suit in the coming months and years. Fedora 18 will likely make the move to Btrfs as the first mainstream/tier-one distribution as right now Fedora, openSUSE, Ubuntu, and others just have Btrfs as an alternate install-time option for the root file-system.
At this time there's no word when Chris Mason will recommend the new btrfs-progs use in mass / merge it to master. Until then, obviously use the new "btrfsck" at your own risk. There's also no word on when any other repair functionality will be added to this file-system checker utility. At least the code is finally available to begin repairing Btrfs file-systems if left in a bad state, after it's been a "work in progress" for what seems like ages. Btrfs has been in the mainline Linux kernel since 2009.