Just a friendly warning: BTRFS isn't anywhere near as robust as ZFS, which in turn has had a long history of problems. There were some threads on HN related to

Just a friendly warning: BTRFS isn't anywhere near as robust as ZFS, which in turn has had a long history of problems. There were some threads on HN related to BTRFS which made me look into its suitability as a RAID5 or RAID6 file system, and what I saw made me back-pedal very fast. Its support for RAID1 or RAID10 (mirroring or stripe-mirror) is okay, but it has glaring issues in all other modes that have gone unresolved for many years. There are some fundamental design issues that might mean that these problems will never get solved, with data loss or data corruption being the inevitable consequence. Storage is like multi-threading: you've either mathematically proved the correctness of your algorithm, or it is Wrong with a capital W. Storage is not like a web app where an occasional HTTP/500 is no big deal and recoverable. You stuff up something even a tiny bit, and the consequence is shredded or lost data and a very bad day for someone somewhere. I'm just not seeing the right attitude from the team working on BTRFS. They've been very lax about data integrity issues, recovery from expected failures, etc... My advice is: stay away.