Hi Chris, On Fri, 5 Apr 2019 at 17:45, Chris Murphy <li...@colorremedies.com> wrote: > > On Thu, Apr 4, 2019 at 11:51 PM Glenn Trigg <ggtr...@gmail.com> wrote: > > > > Hi Chris, > > > > Thanks for spending the time and energy to help me look into this. > > > > btrfs restore isn't very happy either, so I guess I'll wait until > > btrfs-progs v5.0 comes out and see if that helps. > > > > btrfs restore says... > > % ./btrfs restore -v -D /dev/sda1 /data2 > > This is a dry-run, no files are going to be restored > > parent transid verify failed on 628168376320 wanted 37601 found 37712 > > parent transid verify failed on 628168376320 wanted 37601 found 37712 > > parent transid verify failed on 628168376320 wanted 37601 found 37712 > > parent transid verify failed on 628168376320 wanted 37601 found 37712 > > Ignoring transid failure > > ERROR: child eb corrupted: parent bytenr=628624064512 item=0 parent > > level=1 child level=1 > > Error searching -5 > > I'm gonna suggest that's a bug, just because btrfs restore needs to be > expected to do better than this. I suggest taking a btrfs-image while > waiting for btrfs-progs 5.0. > > # btrfs-image -c9 -t4 -ss -w /dev/ /pathtoimage/
I ran this command (using version 4.20.2) and after a whole bunch of WARNING: cannot find a hash collision for ... type messages it then produced this output: Couldn't map the block 1350591496192 Invalid mapping for 1350591496192-1350591512576, got 1469008838656-1470082580480 Couldn't map the block 1350591496192 bad tree block 1350591496192, bytenr mismatch, want=1350591496192, have=0 ERROR: unable to read log root block ERROR: create failed: No such file or directory and no output file was created. This doesn't look very good! Regards, Glenn
