Hello and good day to you.
Upon dispatching several DELETE VM requests over ProxMox API on an LVM-Thin storage node, ProxMox VE fails to remove several disks regarding snapshots and the VM itself after multiple attempts of acquiring VM's disks lock.
The log reads:
trying to acquire lock...
trying to acquire lock...
trying to acquire lock...
... cannot remove disk 'snap1-basevm12000'...
This problem stems from running DELETE operations asynchronously, hence if I do it synchronously (delete VMs one by one) with 'purge' and 'destroy_unreferenced_disks' both set to TRUE, it successfully manages to delete all the disks connected to that VM.
Why does this happen? Is this a limitation related to LVM-Thin storage technology?
Many thanks in advance for your attention.
Upon dispatching several DELETE VM requests over ProxMox API on an LVM-Thin storage node, ProxMox VE fails to remove several disks regarding snapshots and the VM itself after multiple attempts of acquiring VM's disks lock.
The log reads:
trying to acquire lock...
trying to acquire lock...
trying to acquire lock...
... cannot remove disk 'snap1-basevm12000'...
This problem stems from running DELETE operations asynchronously, hence if I do it synchronously (delete VMs one by one) with 'purge' and 'destroy_unreferenced_disks' both set to TRUE, it successfully manages to delete all the disks connected to that VM.
Why does this happen? Is this a limitation related to LVM-Thin storage technology?
Many thanks in advance for your attention.