On Friday 03 March 2017 09:00:10 Qu Wenruo wrote: > > FWIW, as per my later messages, after mounting with clear_cache and > > letting > > btrfs-cleaner finish, btrfs-check did *not* print out those errors after > > running again. It's now about two weeks later that the file system is > > showing problems again. > > If btrfs-check didn't print out *any* error, then it should be mostly > fine. (Unless there is some case we don't expose yet) > > The problem should be caused by kernel AFAIK.
So you think it could be a regression in 4.9? Should I try 4.10? Or is it more likely just an undiscovered bug? > > Oh, and just in case it's relevant, the file system was created with > > btrfs- > > convert (a long time, maybe 1.5 years ago, though; it was originally > > ext4). > > Not sure if it's related. > But at least for that old convert, it's chunk layout is somewhat rare > and sometimes even bug-prone. > > Did you balance the btrfs after convert? If so, it should be more like a > traditional btrfs then. Yes, I'm fairly certain I did that, as that is what the btrfs wiki recommends. > Personally speaking I don't think it is relative for your bug, but much > like a normal extent tree corruption seen in mail list. OK, so is there anything else I can do? Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
signature.asc
Description: This is a digitally signed message part.
