Chris Murphy posted on Wed, 17 Sep 2014 12:57:59 -0600 as excerpted: > But I think you're onto something, that a good superblock can point to a > corrupt tree root, and then not have a straight forward way to mount the > good tree root. If I understand this correctly.
This is what I ran into myself a couple months ago. I ended up doing a restore as the simplest recovery I could do, then recreated the affected filesystems. It happened on two filesystems (separate, I don't trust subvolumes precisely because it's the same filesystem underneath and that's too many eggs in one basket for my comfort), /var/log and /home. I was able to restore nearly all of /home (enough that I wasn't aware of anything missing except symlinks that restore doesn't work with), but lost about half of /var/log, which I did first and made a couple mistakes on that I didn't repeat on /home. I figured there was a way to fix the filesystems as they were, but these threads about deliberately corrupting the first superblock in ordered to use the others hadn't appeared yet, and between restore and backups I got enough back not to be worried about the rest, so restore was "good enough". -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
