[Borgbackup] borg and vm backup

[Thomas Waldmann]

> c61342bdebbcdbaeb37473d76e4a3e06
> /mnt/src/vmbck/daily/Soekris3/Soekris3-2018-11-15_01-15-01/Soekris3-1-flat.vmdk

so i assume the above is the original file.

> c61342bdebbcdbaeb37473d76e4a3e06
> /mnt/borg/restore/src/20181115/mnt/src/vmbck/daily/Soekris3/Soekris3-2018-11-15_01-15-01/Soekris3-1-flat.vmdk

this is the file accessed via "borg mount" ?

> 79f8b416f4073e3e9a40da8989043073
> /mnt/borg/restore/tgt/Soekris3/Soekris3-2018-11-15_01-15-01/Soekris3-1-flat.vmdk

and this the one extracted using "borg extract"?

can you reproduce this? also on another machine?

can you check the memory (memtest86+) and disk (smartctl -t long) of the
machine that behaves strange?

does sha512sum also give different results?

> suppose because I use thin provisioning so the vmdk is a sparse file and
> maybe the restore process restore it as a thick provisioned file.

that is not relevant for md5sum, sparse ranges will still be read as
zero bytes, same as if you have "on disk" zero bytes.

if you do not find a hw or sw issue outside of borg, please file a bug
on github and give more information there (see bug template).

-- 

GPG ID: 9F88FB52FAF7B393
GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393