Nothing works anymore "can't lock file '/run/lock/lxc/pve-config-xxx.lock"

[Noobie]

Hello everyone,

I have integrated an SMB share into an lxc. I then deleted this network folder using gui. However, this folder is still visible as unused disk 0 under the resources.

Deleting it does not work, then the error message appears:

can't lock file '/run/lock/lxc/pve-config-190.lock' - got timeout (500)

Then I shut down the container and wanted to delete this unused disk 0 again via GUI. Error message:

can't lock file '/run/lock/lxc/pve-config-190.lock' - got timeout (500)

Then I tried to restart the container and the error message appears:

TASK ERROR: can't lock file '/run/lock/lxc/pve-config-190.lock' - got timeout

Restoring a backup does not work either

unable to restore CT 190 - can't lock file '/run/lock/lxc/pve-config-190.lock' - got timeout (500)

Deleting the container does not work either

TASK ERROR: can't lock file '/run/lock/lxc/pve-config-190.lock' - got timeout

So now nothing works anymore... Do you have any ideas to solve this issue?

 

[sw-omit]

1. Can you still make new VM's and/or change other VM's? (So is it limited to this VM or the whole system)
2. Does the command qm unlock 190 work to unlock the VM?
3. Else you could also see if something is locking the file with lslocks (do be carefull with "just" killing a process or removing the files though, [1] )

[1] https://forum.proxmox.com/threads/should-there-always-be-lock-files-in-the-var-lock-folders.103458/

 

[Squ1sh]

Hi,
i had a similar issue with smb in a debian lxc. After upgrading to the latest version, it just hang with 100% cpu usage after a while.
Only deleting the .lock file and rebooting the proxmox node helped.
I'm still a bit dissapointed in proxmox (8.2.4) here, that it cannot forcefully stop a container that does not play rules.

Will revert back to an older (05/2023) smb version which seemed to be running finer (only crashes after a few days which needed a restart of the lxc)