looking like I'll get credited as bug reporter for a Linux btrfs bug: patch and bug report
this is silver lining on how it has become harder over time for me to whole-heartedly recommend btrfs, especially to "ordinary" Linux end users... I think I'd still do it on balance? But I'd say a backup strategy is not optional. (But maybe I'd say that anyway.)
see also: my backup strategy
like this
Ben Weinstein-Raun
in reply to Ben Millwood • •Ben Millwood
in reply to Ben Weinstein-Raun • •Ben Weinstein-Raun likes this.
Ben Weinstein-Raun
in reply to Ben Millwood • •Looking around on the internet for other issues just now, it's also apparently pretty common to run into showstopper bugs when trying to do zfs send or zfs receive on encrypted zpools. I've never tried it but that does seem pretty bad.
And yeah, that USB issue sure looks annoying :/
Ben Millwood
in reply to Ben Weinstein-Raun • •Ben Weinstein-Raun likes this.
Ben Weinstein-Raun
in reply to Ben Millwood • •Ben Millwood likes this.
Ben Millwood
in reply to Ben Millwood • •Detailed timeline:
- 26th Sep 2024: I report the bug to the btrfs mailing list
- 27th Sep: Someone on the list misdiagnoses the bug, and then when I correct them, proposes an incorrect fix (lol)
- Later that day: someone else posts the kernel patch
- 30th Sep: Two people review the patch
- 7th Oct: I receive e-mails (because I'm listed as Reported-by on the patch) informing me that the patch has been added to the 6.11-stable, 6.10-stable, 6.6-stable, and 6.1-stable trees.
- 8th Oct: I receive e-mails for three of these patches saying things like "6.6-stable review patch. If anyone has any objections, please let me know."
- 10th Oct: Tags 6.6.55, 6.10.14, 6.11.3 get added to the Linux kernel tree. From reading their
... show moreDetailed timeline:
From report to using the fix in a stable kernel in a stable release of my distro was a total of like... 2-3 weeks? Seems pretty good to me :)
like this
Ben Weinstein-Raun and Daniel Filan like this.