Backup of KVM failing with: Failed to get shared "write" lock.
-
Backup of KVM fails with this error:
Info ExternalAPIException: Failed to execute remote command: [LC_ALL=C sudo qemu-img info --backing-chain /var/lib/libvirt/images/administrative/K8S_Alpn_MSTR-01.qcow2-vProtect-89b59650-dd1a-4167-8f65-fe3a573b7c74], return code: 1, error: [qemu-img: Could not open '/var/lib/libvirt/images/administrative/K8S_Alpn_MSTR-01.qcow2-vProtect-89b59650-dd1a-4167-8f65-fe3a573b7c74': Failed to get shared "write" lock Is another process using the image [/var/lib/libvirt/images/administrative/K8S_Alpn_MSTR-01.qcow2-vProtect-89b59650-dd1a-4167-8f65-fe3a573b7c74]? ]
It occurs either in scheduled multisession backups or in manual (on-demand) backup.
Storware Version 6.1.0-16
QEMU emulator version 6.2.0 (qemu-kvm-6.2.0-20.module+el8.7.0+16905+efca5d32.2)P.S.
I don't think, that the problem is on the KVM-host,
'cause we had not such error on previous version of Storware (6.0.0-35),
the same KVM-host backups were working good,
but sometimes, we had the "Server has encountered the runtime error."
error on Storware 6.0.0-35 Version. -
Update:
There are no errors while backing up brand new VMs.
Error are occuring only on the same VMs, that were backing up already many times on our previous StorWare installations. -
Hi @KLM
Error which you sent is known and is in under development. We will update you when fix will be available.
Regards
-
Hi!
After deep analysis we found, that issue is caused by deleting of snapshots files without merging it to vm. We do not this kind of operation, so it could be done only by user itself.
Regards
-
A admin locked this topic on