You're right, Btrfs has HAD issues. HOWEVER all known corruption bugs, all failed recovery bugs and the likes have been sorted out. Btrfs biggest "issue" right now is the lack of an fsck.btrfs which is only an issue for automatically running fsck on boot, for manually running fsck there is btrfsck. Unfortunately there wont be an fsck.btrfs until the fsck developers do the API changes that the btrfs devs have requested so that all of btrfs fsck-related features can be used.
Originally Posted by ultimA
And yes, I have had ONE failure of btrfs and that was due to a power outage mid-update. It is very possible (though unfortunately impossible to prove or disprove) that if there was an fsck.btrfs in the initrd that it would have detected a dirty-shutdown and automatically run fsck and recovered the filesystem no problem. I could have also tried running btfsck from the live environment, but as I said...it was a brand new install, I didnt really care enough to bother trying to fix it, i just did a reinstall.
I agree that btrfs needs time to mature and grow before being fully marked as "Work environment stable." That being said, btrfs (on recent kernels) I do believe is "Home environment stable." So whether or not btrfs is "stable" really comes down to the environment at hand and your general guidelines for what is "stable."