Device or resource busy using LVM Snapshots

joelserrano

Renowned Member
Mar 16, 2011
33
0
71
Hi,

Im trying out the snapshot feature:

Code:
proxmox:/storage# vzdump --dumpdir . --snapshot 111
INFO: starting new backup job: vzdump --dumpdir . --snapshot 111
INFO: Starting Backup of VM 111 (qemu)
INFO: running
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO:   Logical volume "vzsnap-prxdell1-0" created
INFO: creating archive './vzdump-qemu-111-2012_05_30-17_23_58.tar'
INFO: adding './vzdump-qemu-111-2012_05_30-17_23_58.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/dev/vzpve/vzsnap-prxdell1-0' to archive ('vm-disk-scsi0.raw')
INFO: Total bytes written: 3158310912 (2.35 MiB/s)
INFO: archive file size: 2.94GB
[COLOR=#ff0000]INFO:   device-mapper: remove ioctl failed: Device or resource busy[/COLOR]
[COLOR=#ff0000]INFO:   Unable to deactivate vzpve-vm--111--disk--1-real (254:224)[/COLOR]
INFO:   Logical volume "vzsnap-prxdell1-0" successfully removed
INFO: Finished Backup of VM 111 (00:21:37)
INFO: Backup job finished successfuly
proxmox:/storage#

Can anyone tell me what the error in red means?

FYI: The VM 111 is KVM and was running when I did the snapshot backup. If there is more information required that I'm not posting please let me know.

Thanks in advanced.

Regards,
Joel.
 
also post your 'pveversion -v'
 
Hi Tom,

This is the output from pveversion -v:

Code:
prxdell1:/storage# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4
prxdell1:/storage#

We are currently in the process of installing two new proxmox servers on v2 and migrate all VMs there...


Regards,
Joel.
 
as you already migrate why should you hunt for already fixed bugs?

I suggest you do an offline backup and then a restore on the new 2.1 host.