2 ms·
(a) It's easy to reproduce. There are exact steps in the bug and in the mailing list thread. In fact, the steps are so simple I'll tell you what they are: (1
by rwmj 14y ago
(a) It's easy to reproduce. There are exact steps in the bug and in the mailing list thread. In fact, the steps are so simple I'll tell you what they are: (1) Run mkfs.btrfs, (2) Run any btrfs command on the filesystem. Put (1) + (2) into a shell script so they run immediately after each other. Put a loop around it so it tries over and over again. Bang => data corruption.
(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.
- rlpb 14y ago> (a) It's easy to reproduce, if anyone had put any effort in at all. 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?
- nnnnni 14y agoWait, why would you format the fs, do something with it, format the fs, do something with it, and so on? Isn't one pass enough?
- rwmj 14y agoBecause it's a test designed to reproduce a bug. We hit the bug all the time in libguestfs which spends much of its time formatting filesystems and immediately using them, but it doesn't happen 100% of the time. It's a race condition somewhere.