We have been using Proxmox for several years, now, and it's been working pretty well. However, we recently went to clone a VM (which we have been able to successfully do in the past) and have encountered an issue. The backup (performed using vzdump --tmpdir=/mnt/pve/vm_backupsSAN/tmp/ --dumpdir=/mnt/pve/vm_backupsSAN/ 188, we have also done with and without compression and stdexcludes) works and does not return any error messages. The location it is backing up to is an NFS share.
Verifying or restoring the backup has yielded the same failure in different places based on whether or not compression is enabled, and we have tried all backups on two different nodes in our cluster to confirm that it's not machine-specific.
The latest backup we tried using the backup command above gave the following result:
root@node2:~# vma verify -v /mnt/pve/vm_backupsSAN/vzdump-qemu-188-2015_03_30-11_55_45.vma
CFG: size: 310 name: qemu-server.conf
DEV: dev_id=1 size: 16106127360 devname: drive-virtio0
DEV: dev_id=2 size: 107374182400 devname: drive-virtio1
CTIME: Mon Mar 30 11:55:49 2015
progress 1% (read 1234829312 bytes, duration 3 sec)
progress 2% (read 2469658624 bytes, duration 8 sec)
progress 3% (read 3704422400 bytes, duration 14 sec)
** ERROR **: verify failed - wrong vma extent header chechsum
aborting...
Aborted
I have seen other threads where it was a memory error, but those appear to be cases where the users only had one system to work with. Another item mentioned was disabling compression, but that has only changed the location at which the checksum error is found.
Verifying or restoring the backup has yielded the same failure in different places based on whether or not compression is enabled, and we have tried all backups on two different nodes in our cluster to confirm that it's not machine-specific.
The latest backup we tried using the backup command above gave the following result:
root@node2:~# vma verify -v /mnt/pve/vm_backupsSAN/vzdump-qemu-188-2015_03_30-11_55_45.vma
CFG: size: 310 name: qemu-server.conf
DEV: dev_id=1 size: 16106127360 devname: drive-virtio0
DEV: dev_id=2 size: 107374182400 devname: drive-virtio1
CTIME: Mon Mar 30 11:55:49 2015
progress 1% (read 1234829312 bytes, duration 3 sec)
progress 2% (read 2469658624 bytes, duration 8 sec)
progress 3% (read 3704422400 bytes, duration 14 sec)
** ERROR **: verify failed - wrong vma extent header chechsum
aborting...
Aborted
I have seen other threads where it was a memory error, but those appear to be cases where the users only had one system to work with. Another item mentioned was disabling compression, but that has only changed the location at which the checksum error is found.
