CT is locked (snapshot-delete)
- Thread starter Talha
- Start date
@Talha
pct unlock <ID>
qm manages the qemu VMs while pct is for containers (lxc). To unlock containers you need to use command:
pct unlock <ID>
More info on pct commands below
https://pve.proxmox.com/pve-docs/pct.1.html
Last edited:
Hi, I'm getting similar issue, however in happens from time to time on same container. Container is NOT really funky, has no special options, it's unprivileged. Any advise on how I could diagnose why this specific container get's locked for no reason ?
Hi,
what kind of lock do you get? Was the corresponding operation really successful? You can check the task log for details.
So this seems to happen after a backup. For some reason backup fails, and finishes with "unexpected status"
And the backup job log just abruptly ends there with nothing more ...
after that starting the CT finishes with:
Code:
INFO: Starting Backup of VM 113 (lxc)
INFO: Backup started at 2023-07-11 06:00:14
INFO: status = running
INFO: CT Name: data-logger
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-113-2023_07_11-06_00_14.tar'And the backup job log just abruptly ends there with nothing more ...
after that starting the CT finishes with:
Code:
TASK ERROR: CT is locked (snapshot-delete)
Last edited:
Sounds like it got stuck removing the snapshot created during backup. But it's strange that the log ends where it does. Please share the output of
pct config 113 --current and pveversion -v.I've removed the description section since includes some sensitive information.
Code:
$ pct config 113 --current
arch: amd64
cores: 4
features: nesting=1
hostname: data-logger
memory: 4096
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=6A:7C:73:9E:7A:F2,ip=dhcp,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-zfs:subvol-113-disk-0,size=128G
swap: 0
unprivileged: 1
Code:
$ pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve)
pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e)
pve-kernel-5.15: 7.4-4
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-2-pve: 5.15.39-2
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1It seems to have been solved by running the backup manually.
But have to see if the nightly backup will run tonight
Since this is the CT (LXC container) the appropriate commands are these (found on https://blog.paranoidpenguin.net/2023/04/proxmox-ve-task-error-ct-is-locked-snapshot-delete/, you'll need to run them in PVE shell):
pct unlock 102
and also delete the failed snapshot:
pct delsnapshot 102 vzdump
After these two commands the LXC containter should be startable.
pct unlock 102
and also delete the failed snapshot:
pct delsnapshot 102 vzdump
After these two commands the LXC containter should be startable.