Funny to hear your success; I've managed to break almost every mirror I've entrusted to BTRFS! How? Holding down the power button!
Seemingly regardless of the drives, interface, or kernel, other filesystems paired with LVM or mdraid fail/recover/lie more gracefully. NVMe or SATA (spindles). Demonstrated back-to-back with replacements from different batches.
Truly disheartening, I want BTRFS. I would like to dedicate some time to this, but, well, time remains of the essence. I'm hoping it's something boring like my luck with boards/storage controllers, /shrug.
Well, what are you waiting for? Get your findings to the btrfs-devel mailing list, include your drive make and model. Even better if it's reproducable.
TLDR: busy, lazy, not properly incentivized. I'll get right on that, boss... or is it Officer? I already said: time. I'd like to spend more of my time with triage before I disrupt others, particularly the developers. I don't mind y'all so much :)
It's reproducible, the scope needs to be reduced. With work. A lot of testing and variable change/reduction. More than I care for.
The problem: R&R, work/money, etc, all compete for a limited amount of time. I'll spend it how I like, Square? Comments win over rigorous testing with my schedule, thanks.
Why don't you try to reproduce it? Better things to do, this isn't the mailing list? Exactly. Pick a reason, there's plenty.
Seemingly regardless of the drives, interface, or kernel, other filesystems paired with LVM or mdraid fail/recover/lie more gracefully. NVMe or SATA (spindles). Demonstrated back-to-back with replacements from different batches.
Truly disheartening, I want BTRFS. I would like to dedicate some time to this, but, well, time remains of the essence. I'm hoping it's something boring like my luck with boards/storage controllers, /shrug.