[PVE-User] disk devices not properly cleaned up after removing vm

[Dhaussy Alexandre]

Hello,

Using proxmox 3.4 with SAN shared storage (LVM.)

It seems i have a problem after deleting several vms (from GUI.)
lvs are properly removed but devices are still remaining there on random 
nodes.

root at proxmoxt7:~# clustat
Cluster Status for proxmox @ Fri Apr 24 16:42:51 2015
Member Status: Quorate

  Member Name                                          ID   Status
  ------ ----                                          ---- ------
  proxmoxt7                                                1 Online, 
Local, rgmanager
  proxmoxt8                                                2 Online, 
rgmanager
  proxmoxt9                                                3 Online, 
rgmanager

  Service Name                                Owner 
(Last)                                State
  ------- ----                                ----- 
------                                -----
  pvevm:100 proxmoxt9                                   started


-- On first node :

lvs | grep disk :
   vm-100-disk-1 T_proxmox_1 -wi------ 101.00g

dmsetup ls | grep disk :
T_proxmox_1-vm--101--disk--1    (253:6) <-- should have been deleted
T_proxmox_1-vm--100--disk--1    (253:5)

-- On the second node :

lvs | grep disk :
   vm-100-disk-1 T_proxmox_1 -wi------ 101.00g

dmsetup ls | grep disk :
T_proxmox_1-vm--101--disk--1    (253:5) <-- should have been deleted
T_proxmox_1-vm--107--disk--1    (253:10) <-- should have been deleted
T_proxmox_1-vm--103--disk--1    (253:7) <-- should have been deleted

-- On the third node :

lvs | grep disk :
   vm-100-disk-1 T_proxmox_1 -wi-ao--- 101.00g

dmsetup ls | grep disk :
T_proxmox_1-vm--100--disk--1    (253:5)
T_proxmox_1-vm--106--disk--1    (253:8) <-- should have been deleted


Which results in this error while trying to create a new vm :

device-mapper: create ioctl on T_proxmox_1-vm--101--disk--1 failed: 
Device or resource busy
TASK ERROR: create failed - lvcreate 'T_proxmox_1/pve-vm-101' error: 
Failed to activate new LV.

Fixed by deleting the device manually : dmsetup remove 
T_proxmox_1-vm--101--disk--1


root at proxmoxt7:~# pveversion  -v
proxmox-ve-2.6.32: 3.4-150 (running kernel: 3.10.0-8-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-3.10.0-7-pve: 3.10.0-27
pve-kernel-3.10.0-8-pve: 3.10.0-30
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Regards,
Alexandre.