Readding Btrfslist, and adding Qu: On Thu, Aug 17, 2017 at 12:48 AM, Zirconium Hacker <jared.e.vb@xxxxxxxxx> wrote: > Oh, sorry, I guess the output of the command I ran wasn't clear -- it > was collecting the output of running the debug command on all 1,084 > and showing that it was the same. Here's specifically what you asked > for: > > $ sudo btrfs-debug-tree -b 61809344512 /dev/sda4 > btrfs-progs v4.12 > bytenr mismatch, want=61809344512, have=0 > Couldn't read tree root > ERROR: unable to open /dev/sda4 > $ sudo btrfs-debug-tree -b 1085440000 /dev/sda4 > btrfs-progs v4.12 > bytenr mismatch, want=61809344512, have=0 > Couldn't read tree root > ERROR: unable to open /dev/sda4 > > I'm using GMail, and it's confusing me by trimming off quotes and > stuff, so sorry if I miss something. > OK well now we're in the bad part of Btrfs repair where the error messages don't help. It's one thing for it to complain about 1085440000 being invalid, because by now it might have been overwritten, but to say it wants some other root that we already know it can't read, and then fail reading that root is not helpful information. Maybe Qu has an idea. But it does sound like something really catastrophic happened to blow away all of the backup root trees. Going back to your first email, -o ro,usebackuproot failed with a chunk tree error. I wonder if 'rescue chunk' might help. Try 'btrfs rescue chunk -v' and see what you get. -- 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
