| Everyone in production reproduces this. Intentionally or not, everything on a long enough timeline will suddenly lose power. I'm sorry to offend what is otherwise a decent filesystem, but I, and the systems I'm responsible for, will not use BTRFS with RAID and this characteristic. There's a lot of qualification there, read it again. I would much rather let the journal replay and do its thing, than rebuild the array. Something every alternative offers, consistently. BTRFS RAID has routinely burned me every time I have given it the opportunity. It hasn't survived nearly as much as the other test arrays. I'm fine discussing filesystems, benefits, and all of that - but I can't entertain it when you try to make this so heated. These are anecdotes from reliability tests I've been doing... I'm sharing them so that they can be considered. You accuse me, while opening like this? At least my anecdotes weren't insulting. edit: To add, this isn't something I've kept secret. I don't know why you say that. Have you read every communication I've written? I can show you screenshots that span the last three months discussing this exact situation I haven't reported it upstream because I have better things to do; ship. You might see this, but hopes aren't high. This is about the response I expected. It's an extreme edge case, but it consistently cuts. The filesystem we use is incredibly uninteresting. By design. I find it utterly hilarious you think I'm the only person who has had issues with BTRFS RAID |