Thank you very much Chris and Duncan for your help. I appreciate it. I was able to restore all the files I needed from the filesystem.
- dan On Tue, Aug 25, 2015 at 8:00 PM, Duncan <1i5t5.dun...@cox.net> wrote: > Dan Hentschel posted on Tue, 25 Aug 2015 11:11:44 -0400 as excerpted: > >> I can restore some (all?) of the root fs with btrfs restore: >> >> # btrfs restore /dev/mapper/kingston-streamer2 /mnt checksum verify >> failed on 85360640 found 6934D1E8 wanted C1A46C13 checksum verify failed >> on 85360640 found 6934D1E8 wanted C1A46C13 Csum didn't match offset is >> 20480 failed to inflate: -3 >> >> Unfortunately, this doesn't seem to restore any of the contents of >> /home, which is what I am really hoping to get at. > > Three points: > > 1) As Chris Murphy mentioned but it's worth underlining and expanding... > > While for normal online operations it's the kernel version that's > critical as the userspace code simply forwards requests to the kernel to > do the work, for offline operations such as check and restore the > userspace code is critical, and you really want a current version, as old > versions simply didn't know how to fix problems that newer versions have > code to deal with properly. > > And given the rate of btrfs development, at about two years outdated, > btrfs-progs 3.12 isn't merely old, it's ancient, like the rusty old farm > equipment that hadn't moved in 20 years, that I used to play on as a kid! > > So try updating your userspace, to something current like v4.1.2, and see > if that works better for you. =:^) > > 2) Restore is /much/ improved in current userspace. Among other things, > it can (with the appropriate options) restore ownership/permissions/times > metadata now, as well as symlinks, neither of which it restored before. > > 3) Restore (at least current versions) has options to restore only files > under specific tree roots or by specific path-regex. Additionally, if > it's not finding the files you need restored by default, you can use > btrfs-find-root along with the -t option to point it at an older, perhaps > less damaged, root. There's a wiki page (listed in the current btrfs- > restore manpage) that describes that in a bit more detail, altho last I > checked it was itself a bit dated so you kind of have to play a bit of > matchup between what it says and how the newer version works. In that > regard, the restore --list-roots and --dry-run options can be helpful. > > -- > 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 -- dan B hentschel d...@hentschels.com -- 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
