Oliver Freyermuth posted on Sat, 28 Jan 2017 17:46:24 +0100 as excerpted: >> Just don't count on restore to save your *** and always treat what it >> can often bring to current as a pleasant surprise, and having it fail >> won't be a down side, while having it work, if it does, will always be >> up side. >> =:^) >> > I'll keep that in mind, and I think that in the future, before trying > any "btrfs check" (or even repair) > I will always try restore first if my backup was not fresh enough :-).
That's a wise idea, as long as you have the resources to actually be able to write the files somewhere (as people running btrfs really should, because it's /not/ fully stable yet). One of the great things about restore is that all the writing it does is to the destination filesystem -- it doesn't attempt to actually write or repair anything on the filesystem it's trying to restore /from/, so it's far lower risk than anything that /does/ actually attempt to write to or repair the potentially damaged filesystem. That makes it /extremely/ useful as a "first, to the extent possibke, make sure the backups are safely freshened" tool. =:^) Meanwhile, FWIW, restore can also be used as a sort of undelete tool. Remember, btrfs is COW and writes any changes to a new location. The old location tends to stick around, not any more referenced by anything "live", but still there until some other change happens to overwrite it. Just like undelete on a more conventional filesystem, therefore, as long as you notice the problem before the old location has been overwritten again, it's often possible to recover it, altho the mechanisms involved are rather different on btrfs. Basically, you use btrfs-find-root to get a list of old roots, then point restore at them using the -t option. There's a page on the wiki that goes into some detail in a more desperate "restore anything" context, but here, once you found a root that looked promising, you'd use restore's regex option to restore /just/ the file you're interested in, as it existed at the time that root was written. There's actually a btrfs-undelete script on github that turns the otherwise multiple manual steps into a nice, smooth, undelete operation. Or at least it's supposed to. I've never actually used it, tho I have examined the script out of curiosity to see what it did and how, and it / looks/ like it should work. I've kept that trick (and knowledge of where to look for the script) filed away in the back of my head in case I need it someday. =:^) -- 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
