I filed this serious bug in btrfs about 2 months ago, and nothing has been done about it. This worries me.
1) Appear to be the only one affected by it. 2) Don't have exact steps to reproduce it.
This makes it very difficult for anybody apart from you to work on the issue.
> nothing has been done about it.
From the bug, it looks like lots has been done about it.
> This worries me.
I think this is justified for you, but has little bearing on others. Software projects are full of bugs that only appear to affect one person. These bugs make little progress but don't necessarily reflect on the general quality of the software. Admittedly it is more of a concern on something like a filesystem, but I am still skeptical.
(b) It's a data corrupter. That should be an immediate "stop everything" red flag (for a serious filesystem at least).
Edit: Rereading this comment, I sound like I'm being very negative about btrfs. I just want to say that I really want btrfs to work, because it's based on very sound principles. I've also offered to help immediately testing any proposed patches for this bug.
That's not the impression I get from the bug! I'm sure I read "difficult to reproduce". Perhaps it would help with attention if you made this absolutely clear?
We labor to design a system that stores data safely to a stable medium. This is done while acknowledging that we are not perfect and cannot get everything right. HOWEVER, when we know that we have done something wrong and it can gravely affect a user, we do not ship. Ever. Period.
"Software has bugs" is the lamest excuse to ship something with bugs. Do you think that pacemaker firmware leaves the factory floor with known bugs? I doubt it.