Btrfs
Copy-on-write Linux filesystem with snapshots, checksums, compression and built-in multi-device RAID.
Liked for cheap snapshots, checksums and compression123, and long-time users call it a solid choice that benchmarks faster than ZFS.456 The most common complaint is data corruption that recovery tools could not fix78910, plus warnings about RAID5/6, failed-drive handling and running out of metadata space.111213
Why people recommend it
Snapshots · 3
Commenters use snapshots for rollback, backups and resettable VM environments.
“I use btrfs snapshots on all my devices”
“I then made the guest root directory a BTRFS subvolume, so that I can snapshot it.”
Show 1 more
“Currently, I use Btrfs on Synology, mainly because snapshots and checksums are nice”
Data features · 2
Checksums, reflinks, compression and deduplication are named as reasons to use it.
“Currently, I use Btrfs on Synology, mainly because snapshots and checksums are nice”
“It's grown to be a pretty decent file system.”
Maturity · 3
Long-time users say it has matured, with one reporting no data loss since 2019.
“It's grown to be a pretty decent file system.”
“I use btrfs: it's the most actively tested and developed filesystem in Linux today, by a very wide margin.”
Show 1 more
“Currently, I use Btrfs on Synology, mainly because snapshots and checksums are nice”
Flexibility vs ZFS · 3
Some prefer it to ZFS because it can reshape arrays, ships in mainline Linux and avoids ZFS licensing issues.
“I use btrfs because using zfs has been painful for me”
“fedora fortunately still supports btrfs”
Show 1 more
“I use btrfs: it's the most actively tested and developed filesystem in Linux today, by a very wide margin.”
Performance · 1
One commenter cites a benchmark showing OpenZFS about 35% slower than Btrfs.
“You will find that OpenZFS is ~35% slower than btrfs.”
Caveats and dissent
Data corruption · 3
Several users report unrecoverable filesystems or lost data and have switched away, often to ZFS.
“Btrfs blew up without ANY reason at all in my case.”
“BTRFS was completely irrecoverable after a system crash”
Show 1 more
“I've personally been bitten by data corruption more than once, so I stay away from it now.”
RAID and failures · 2
Users warn to avoid RAID5/6 and say it does not recover well from disappearing or failed drives.
“It's fine if you stay away from it's raid5/6.”
“Btrfs does not auto-recover from this.”
Disk space · 2
Snapshots can fill a drive and cause metadata exhaustion, and one user says it fails when disks fill up.
“experiencing metadata exhaustion probably due to the snapshots filling up my home drive”
“I saw Btrfs die so many times, I know what to suspect.”
Tooling footguns · 2
Even supporters say its operational model and tools have footguns that can cause data loss.
“I use btrfs because using zfs has been painful for me”
“It's grown to be a pretty decent file system.”
Backup restore · 1
One user lost a backup when a btrfs send stream failed with a CRC error on receive.
Concurrency, encryption · 2
Commenters cite heavy contention with concurrent Rust builds and no native encryption.
“Btrfs has massive contention problems with concurrent Rust builds”
“kind of considered Btrfs for this new NAS”
Often compared with
Who recommends it in their own words
Threads where it came up
- Why I (Still) Love Linux ? 3 mentions
- LayerFS: A filesystem for AI coding agents 2 mentions
- Btrfs/ZFS/bcachefs under workloads classic benchmarks skip 2 mentions
- Creating backup storage sucks 2 mentions
- Benchmarking OpenZFS vs. EXT4 for My NAS 2 mentions
- Codex Desktop continuously generates Crashpad pending dumps 1 mention
Also written as btrfs. Data: btrfs.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 26
“i went to a battle and lost all of its data to corruption”
“It's fine if you stay away from it's raid5/6.”
“Btrfs has massive contention problems with concurrent Rust builds”
“Btrfs does not auto-recover from this.”
“Btrfs blew up without ANY reason at all in my case.”
“fedora fortunately still supports btrfs”
“so I don't use btrfs in areas that we need it most”
“Snapshots make this trivial. Particularly in the case of btrfs”
“I use btrfs snapshots on all my devices”
“I used it a couple of years ago and really didn’t have a positive experience.”
“I then made the guest root directory a BTRFS subvolume, so that I can snapshot it.”
“I use BTRFS on MDADM though.”
“experiencing metadata exhaustion probably due to the snapshots filling up my home drive”
“kind of considered Btrfs for this new NAS”
“Currently, I use Btrfs on Synology, mainly because snapshots and checksums are nice”
“run a monthly scrub for my btrfs pool”
“I've personally been bitten by data corruption more than once, so I stay away from it now.”
“There's Docker, OverlayFS, FUSE, ZFS or Btrfs snapshots?”
“You will find that OpenZFS is ~35% slower than btrfs.”
“I saw Btrfs die so many times, I know what to suspect.”
“It's grown to be a pretty decent file system.”
“BTRFS was completely irrecoverable after a system crash”
“I use btrfs: it's the most actively tested and developed filesystem in Linux today, by a very wide margin.”
“I got burned too.”
“I use btrfs for my backups...”
“I use btrfs because using zfs has been painful for me”