Can't delete Containers

A

axion.joey

Active Member
Dec 29, 2009
78
2
28
Hey Everyone,

I have two containers that I can't remove from the web interface. When I attempt to delete them I see this error message.

stat(/var/lib/vz/private/386): No such file or directory
Container is currently mounted (umount first)
TASK ERROR: command 'vzctl destroy 386' failed: exit code 41

Here's the information on the proxmox host
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

And this is what I see when I attempt to delete the container from the CLI.
vzctl delete 386
stat(/var/lib/vz/private/386): No such file or directory
Container is currently mounted (umount first)

I rebooted this specific host and every host in the cluster and I'm still seeing the same issue. Any help would be greatly appreciated.
 
Thanks for the quick response. I just checked and the containers aren't on any other nodes. Yes we do have 4 servers in the cluster
 
So the config file is at ls /etc/pve/openvz/386.conf?

try to unmount manually with

# vzctl umount 386
 
This is what I receive.

vzctl umount 386
stat(/var/lib/vz/private/386): No such file or directory
Can't umount /var/lib/vz/root/386: Invalid argument

There is no folder in /var/lib/vz/private for the 386 vm. So it looks like the vm's data was successfully deleted. Is it safe to just delete /etc/pve/openvz/386.conf?
 
I wonder why vzctl thinks it is still mounted? What is the output of

# cat /proc/mounts

But sure, you can delete the config manually.
 
Here's the output

cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=8243290,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=6596552k,mode=755 0 0
/dev/mapper/pve-root / ext3 rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=13193100k 0 0
/dev/mapper/pve-data /var/lib/vz ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/sda1 /boot ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/fuse /etc/pve fuse rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other 0 0
none /sys/kernel/config configfs rw,relatime 0 0
beancounter /proc/vz/beancounter cgroup rw,relatime,blkio,name=beancounter 0 0
container /proc/vz/container cgroup rw,relatime,freezer,devices,name=container 0 0
fairsched /proc/vz/fairsched cgroup rw,relatime,cpuacct,cpu,cpuset,name=fairsched 0 0
 
You must log in or register to reply here.
Top Bottom