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 res
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 fou
On Tue, Aug 25, 2015 at 9:11 AM, Dan Hentschel wrote:
> Btrfs v3.12
I'd say that version of btrfs-progs is too old for reliable btrfs
check --repair to be much help and could make things worse.
> # btrfs restore /dev/mapper/kingston-streamer2 /mnt
> checksum verify failed on 85360640 found 69
This is a box with 9 VMs residing on it on multiple SSDs, partitioned
with LVM. The particular VM in question is a very simple image, so
it's not all that big of a deal, but there are a few scripts I'd like
to recover from it if possible. The FS that died contains the root and
/home as subvolumes @
This is btrfs with kernel 3.19. (.0-trunk from Debian), on a single volume
(on top of LVM but that should not matter).
I do this, on a freshly-booted system:
# mount /foo
# cd foo
# rsync -aPHAX . /bar
[ after an hour or so ]
^C
# cd ..
# fuser -m /foo
# ps ax | grep "[ /]rsync"
# umount /foo
umou
