Same happened to me. Been a long time btrfs advocate, it just seemed like an ideal modern FS with very useful features, FS-level RAID, CoW, transparent compression, snapshots, automatic TRIM, subvolumes that eliminate the need of LVM in my usecases, no fixed amount of inodes... It's great, until you start hitting problems like fully allocated metadata partition, or some corruption that will keep tainting the FS and it'll refuse to mount, not to mention that there's no tool like 'fsck' for BTRFS and it's easy to further break the FS while attempting to repair it, and the need to regularily balance the FS.
At some point btrfs got corrupted seemingly out of nowhere on my root partition, twice with some time in-between (at first I blamed my drives and reinstalled) and I couln't recover from it, so I simply went back to good old ext4 and it's been working as expected.
Note that I don't run any crazy or experimental options, my standard mount options list was noatime and nodiscard (and the subvolume per mountpoint). The FS itself was in a dm-crypt container though, but BTRFS is supposed to be fully compatible.
Thread collapsed