On Thu, Sep 1, 2016 at 12:51 AM, Paul Jones <paul@xxxxxxxxxxxxxxx> wrote: >> -----Original Message----- >> From: linux-btrfs-owner@xxxxxxxxxxxxxxx [mailto:linux-btrfs- >> owner@xxxxxxxxxxxxxxx] On Behalf Of Chris Murphy >> Sent: Thursday, 1 September 2016 7:59 AM >> To: Btrfs BTRFS <linux-btrfs@xxxxxxxxxxxxxxx> >> Subject: Re: btrfs-progs 4.7, check reports many "incorrect local backref >> count" messages >> >> This is still happening with btrfs-progs 4.7.1 and there is zero information in >> the long result what to do about the problem, and whether it's sane to try >> have --repair fix it, let alone what the original cause of the problem was. > > I just potentially damaged a perfectly good filesystem because of this. I was getting hundreds of "Incorrect local backref count" so I decided to try repair, which seemed to complete ok. I then rescanned without repair and btrfs check eventually crashed with an assertion. That's when I figured something may be wrong. Wait, so you did a --repair and then the following-up check crashes? But does the file system mount and does it still work? The first is bad enough, but if it won't mount this is terrible. -- 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
