That sucks, but is a good indicator of why I won't trust my data to it yet. What was your pool configuration (RAID1/5/6)?I have been running my home server on btrfs pool for the last 2+ years, no problems, but I did lose 2 tb worth of data last week when my 2 drive pool crashed dead. It was not entirely btrfs fault as I had a ram issue and did not know untill it was too late. Also I think I found a bug in btrfs raid. When you uze raw devices
Solaris used to have a similar feature in disksuite. (Way before ZFS; hilariously disk management was part of why they needed ZFS.) You could create a mirror for your root drive, but it needed >50% of the metadata copies to decide that any given configuration was valid. So if you created a two drive mirror, by default it wouldn't boot with only one working drive. This used to really confuse new admins who thought they were setting up something simple, like linux md. Good times. Common theory back then was that sun made disksuite as painful as possible to upsell veritas.That reminds me again - the number one reason I avoided btrfs last time was that if a RAID array degraded, it would refuse to mount... so if you installed on a RAID1 as I'm usually wont to do, and one of your discs failed, your whole machine would be unable to boot without some rather convoluted manual intervention. Unacceptable IMHO.
Are you using Raid-6?I have been using btrfs for the last 2 years without any major issues. Did find a bug when using raw devices though. Lost almost 2tb of media over it.