On Fri, Jun 9, 2017 at 1:57 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: > On Fri, Jun 09, 2017 at 09:12:16PM +0200, Koen Kooi wrote: >> Hi, >> >> Today the kernel got wedged during shutdown (4.11.x tends to do that, haven't >> debugged) and I pressed the reset button. The next boot btrfs won't mount: >> >> [Fri Jun 9 20:46:07 2017] BTRFS error (device md0): parent transid verify failed on 5840011722752 wanted 170755 found 170832 >> [Fri Jun 9 20:46:07 2017] BTRFS error (device md0): parent transid verify failed on 5840011722752 wanted 170755 found 170832 >> [Fri Jun 9 20:46:07 2017] BTRFS error (device md0): failed to read block groups: -5 >> [Fri Jun 9 20:46:08 2017] BTRFS error (device md0): open_ctree failed > > With a transid failure on mount, about the only thing that's likely > to work is mounting with -o usebackuproot. If that doesn't work, then > a rebuild of the FS is almost certainly needed. Weird that it wants almost 80 generations back from what's found. Sounds like betrayal somewhere... I'd say take a btrfs-image and put it up somewhere and also file a bug. The fsck should not crash. What are these showing? # btrfs insp dump-s -f /dev/ # btrfs rescue super /dev/ # btrfs-find-root /dev/ -- 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
