On Sat, Jan 9, 2016 at 2:04 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: > On Sat, Jan 09, 2016 at 09:59:29PM +0100, cheater00 . wrote: >> OK. How do we track down that bug and get it fixed? > > I have no idea. I'm not a btrfs dev, I'm afraid. > > It's been around for a number of years. None of the devs has, I > think, had the time to look at it. When Josef was still (publicly) > active, he had it second on his list of bugs to look at for many > months -- but it always got trumped by some new bug that could cause > data loss. Interesting. I did not know of this bug. It's pretty rare. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
