Do you have the logs (engine.log, vdsm.log) for this?
qemu-nbd holding the lock might mean the transfer was not finalized
properly and the nbd server was left open which should not happen...
On Wed, Aug 31, 2022 at 1:57 PM Diego Ercolani <diego.ercolani(a)ssis.sm> wrote:
Thanks Arik,
we have tried your solution but with no successful results.
we have gather also other infor and combined in this solution:
we have deleted on DB the row on vm_backups and vm_disk_map related to the hanged
backup.
The we have tried to delete shapshot locked , after the row db deletion the messange
"cannot delete shapshot during backup operations" does not apper" but
deletion failed anyway.
so we watch the log file /var/log/ovirt-engine/engine.log ans see this messages
nIs another process using the image [
/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4
then we search on the node which process olds the file with the command:
lsof | grep f17c3443-b62f-43f5-b35c-5ba9225abaf4
and we found on a node that the file was in use by a process qemu-ndb
we kill that process and finally we were enabled to delete the shapshot.
Thanks again for your support
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LX7ZZTJVUI6...