vma verify failed - got wrong block address

[Vladimir.B]

Good day!
pveversion: pve-manager/5.4-6/aa7856c5 (running kernel: 4.15.18-14-pve)
the backup is successful, then run the command:
vma verify vzdump-qemu-xxx-xxx.vma

and see error:

** (process:16208): ERROR **: verify failed - got wrong block address - write beyond end
Trace/breakpoint trap

and restore fails with error:

** (process:9108): ERROR **: restore failed - got wrong block address - write beyond end
temporary volume 'local-zfs_vms:xxx/vm-xxx-disk-0.raw' sucessfuly removed
no lock found trying to remove 'create' lock
command 'set -o pipefail && vma extract -v -r /var/tmp/vzdumptmp9107.fifo /pool2/backups/dump/vzdump-qemu-xxxxxx.vma /var/tmp/vzdumptmp9107' failed: got signal 5


Please help in fixing the problem.

Best regards!

 

[LnxBil]

Please help in fixing the problem.

Use another backup file and periodically check backup files for errors after creating them.

 

[Vladimir.B]

Use another backup file and periodically check backup files for errors after creating them.

Thanks for the advice. Other backups are also not restored. The problem occurs on two of the four servers.

 

[LnxBil]

The problem occurs on two of the four servers.

So, a lot of backup files got corrupted somehow? Have you a statistic how much?

 

[Vladimir.B]

So, a lot of backup files got corrupted somehow? Have you a statistic how much?

some backups from two of the four servers cannot be restored to all four servers.

 

[LnxBil]

some backups from two of the four servers cannot be restored to all four servers.

If they're corrupt on one one server, they most probably cannot be read from others. Are the backups stored local or on a network share?

 

[Vladimir.B]

The backup of existing machines stored local and on NFS share and there and there recovery with an error.
If I create a new machine and backup it, the recovery is successful.