[PVE-User] VM remains in snap-delete state

[Mark Schouten]

Hi,

I have a VM that remains in snap-delete state. I'm wondering what the
safest way is to proceed. I think I can do a qm unlock, and click
remove again, but I'm not sure. Please advise. See current qm config
below:

***@proxmox01:~# cat /etc/pve/qemu-server/111.conf 
#REDACTED
balloon: 8192
boot: cdn
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
lock: snapshot-delete
memory: 24576
name: tux178
net0: bridge=vmbr999,virtio=66:36:62:35:64:65,tag=229
net1: bridge=vmbr999,virtio=66:32:38:63:63:33,tag=3
numa: 0
ostype: l26
parent: Just_before_polpoly_10_16_5_fp1
smbios1: uuid=5f30d44f-2685-4072-b8d6-1f9e3b8c57fc
sockets: 1
virtio0: rbd:vm-111-disk-1,size=1T

[Just_before_polpoly_10_16_5_fp1]
balloon: 8192
boot: cdn
bootdisk: virtio0
cores: 4
ide2: none,media=cdrom
machine: pc-i440fx-2.9
memory: 32768
name: tux178
net0: bridge=vmbr999,virtio=66:36:62:35:64:65,tag=229
net1: bridge=vmbr999,virtio=66:32:38:63:63:33,tag=3
numa: 0
ostype: l26
smbios1: uuid=5f30d44f-2685-4072-b8d6-1f9e3b8c57fc
snapstate: delete
snaptime: 1526563253
sockets: 1
virtio0: rbd:vm-111-disk-1,size=1T
vmstate: rbd:vm-111-state-Just_before_polpoly_10_16_5_fp1

[Mark Schouten]

Hi,

Post by Mark Schouten
I have a VM that remains in snap-delete state. I'm wondering what the
safest way is to proceed. I think I can do a qm unlock, and click
remove again, but I'm not sure. Please advise. See current qm config

Just found the following error in the task list:
trying to aquire cfs lock 'storage-REDACTED' ...TASK ERROR: got lock
request timeout

I see the snapshot still exists, as does the state-image. Would the
best solution be to just qm unlock and click delete snapshot again?

[Alwin Antreich]

Post by Mark Schouten
Hi,

Post by Mark Schouten
I have a VM that remains in snap-delete state. I'm wondering what the
safest way is to proceed. I think I can do a qm unlock, and click
remove again, but I'm not sure. Please advise. See current qm config

trying to aquire cfs lock 'storage-REDACTED' ...TASK ERROR: got lock
request timeout
I see the snapshot still exists, as does the state-image. Would the
best solution be to just qm unlock and click delete snapshot again?

The lock was not acquired, that's why it ran into the timeout. You need to
find out what other task is holding the lock and get that one to complete
first.

--
Cheers,
Alwin