kennysinkeler

New Member
Oct 1, 2016
6
0
1
25
Hi,
i have the following problem.
If i delete a vm and later i create a new vm with de same id.
Then i get the following error:
device-mapper: create ioctl on vmdata-vm--105--disk--0LVM-Kv4PpUAk4B73jkQAHVozUVypVNy97MUKP4Eb0l3BbxvgAIXeXV21HYLEl4h3CEHs failed: Device or resource busy
TASK ERROR: unable to create VM 105 - error with cfs lock 'storage-vmdata': lvcreate 'vmdata/pve-vm-105' error: Failed to activate new LV.


The old disk shows up with the command:
dmsetup ls | grep vmdata

I have found two less then ideal fixes for this issue.
1. reboot the node.
2. dmsetup remove {{disk}}

What can i do the fix the cause of problem

Greetz,
Kenny
 
please post the output of `pveversion -v`
also post the complete log of the create task
Thanks!
 
Hi @Stoiko Ivanov,
This al complote log of the create task(what i can found)


Code:
Task viewer: VM 105 - Create

Output
device-mapper: create ioctl on vmdata-vm--105--disk--0LVM-Kv4PpUAk4B73jkQAHVozUVypVNy97MUKP4Eb0l3BbxvgAIXeXV21HYLEl4h3CEHs failed: Device or resource busy
TASK ERROR: unable to create VM 105 - error with cfs lock 'storage-vmdata': lvcreate 'vmdata/pve-vm-105' error: Failed to activate new LV.


pveversion-v:
Code:
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve) 
pve-manager: 5.3-5 (running version: 5.3-5/97ae681d)  
pve-kernel-4.15: 5.2-12        
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1                        
criu: 2.11.1-1~bpo90                   
glusterfs-client: 3.8.8-1                      
ksm-control-daemon: 1.2-2               
libjs-extjs: 6.0.1-2                             
libpve-access-control: 5.1-3             
libpve-apiclient-perl: 2.0-5              
libpve-common-perl: 5.0-43           
libpve-guest-common-perl: 2.0-18      
libpve-http-server-perl: 2.0-11             
libpve-storage-perl: 5.0-33                 
libqb0: 1.0.3-1~bpo9                    
lvm2: 2.02.168-pve6                    
lxc-pve: 3.0.2+pve1-5                 
lxcfs: 3.0.2-2                               
novnc-pve: 1.0.0-2                       
proxmox-widget-toolkit: 1.0-22      
pve-cluster: 5.0-31                        
pve-container: 2.0-31                  
pve-docs: 5.3-1                          
pve-edk2-firmware: 1.20181023-1           
pve-firewall: 3.0-16                                      
pve-firmware: 2.0-6                                 
pve-ha-manager: 2.0-5                                  
pve-i18n: 1.0-9                                
pve-libspice-server1: 0.14.1-1            
pve-qemu-kvm: 2.12.1-1                     
pve-xtermjs: 1.0-5                                
qemu-server: 5.0-43                            
smartmontools: 6.5+svn4324-1                                                                                                                            spiceterm: 3.0-5                         
vncterm: 1.5-3                                                                                                                                          zfsutils-linux: 0.7.12-pve1~bpo1
 
please upgrade to the latest version - I believe there were a few fixes in that area recently.
should the issue persist, please report it again here
Thanks
 

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!