3 ms·

I might be the minority here, but I've been burned twice with btrfs (in Q3 and Q4 of 2014) and was only able to recover the data with great effort. Both times t

I might be the minority here, but I've been burned twice with btrfs (in Q3 and Q4 of 2014) and was only able to recover the data with great effort. Both times the errors only occurred after extended use and without a clear cause. My (unfortunately necessarily vague) bug report was met with scepticism whether my hardware was at fault (I ran memtest for 48h without any errors, and never had any problems with other filesystems), which was quite frustrating after I had lost a significant amount of time on their experimental filesystem and at least wanted to help others not have the same problems in the future. I'll consider btrfs again when a large distribution has adopted it as default and it has worked for them for at least a year.

someuser2723 11y ago
For what it's worth, SLES 12 was released October 2014 and has btfs by default: https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#intro.new https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#intro... openSUSE also has it default in 13.2 (November 2014): https://en.opensuse.org/Portal:13.2 https://en.opensuse.org/Portal:13.2
- rleigh 11y ago
  Yes, and I still wonder at the sanity of making it the default given the large number of known problems. I've lost data, irrecoverably, with Btrfs on at least two occasions--the filesystem was completely toasted. More recently I've encountered the unbalancing issue--the filesystem would become read-only approximately every 36 hours with sustained intensive use. That's simply unacceptable--the default filesystem needs to be utterly reliable, and becoming unusable at unpredictable intervals is not suitable for production.