[SOLVED] unable to unlock a locked container after failed backup

odix67

Member
Jun 11, 2020
1
0
21
57
Hi
after a failed backup (device runs out of disk space) of a container, the container status was usually locked. The command:
Bash:
root@something:~# pct unlock 3002
unable to open file '/etc/pve/nodes/something/lxc/3002.conf.tmp.11948' - Input/output error
doesn't work. After some investigation and some trails I've noticed that the cluster service was in a not so good shape ;-), it was just in a read-only mode.
I decided to restart the cluster service
Bash:
systemctl restart pve-cluster.service
after doing this, I was unable to unlock the container

BR odi

btw: it is single node, running pve 6.2-4
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!