On Wed, Jun 07, 2017 at 01:10:26PM +0300, Timofey Titovets wrote: > 2017-06-07 13:05 GMT+03:00 Stefan G. Weichinger <lists@xxxxxxxx>: > > Am 2017-06-07 um 11:37 schrieb Timofey Titovets: > > > >> btrfs scrub start /mnt_path do this trick > >> > >> After, you can find info with paths in dmesg > > > > thank you, I think I have the file, it's a qemu-img-file. > > I try cp-ing it to another fs first, but assume this will fail, right? > > Yes, because btrfs will return -EIO > So try dd_rescue Or even plain dd conv=noerror. Both will do a faithful analogue of a physical disk with a silent data corruption on the affected sectors. It might be a better idea to try running the VM in question: it will avoid silencing the errors, thus let you find out what you lost -- if you run any filesystem other than btrfs or zfs in the guest, it has no means of spotting silent corruption. Obviously, do make the dd copy first. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A tit a day keeps the vet away. ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ (Rejoice as my small-animal-murder-machine got unbroken after ⠈⠳⣄⠀⠀⠀⠀ nearly two years of no catch!) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
