vzdump failed - Device or resource busy

[psauxw]

Hi!
I got this problem for the 1st time in maybe 2-3 weeks (upgraded from 1.9 to 2.3)
The vzdump script could not backup ANY of the 15 VMs running. All with the same error.
Is there a way to hrm ... fix this?

Thank you very much

proxmox:/dev/pve-san# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-95
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1


vzdump 101 104 105 106 107 108 116 134 139 109 115 133 --quiet 1 --mailto xxx@xxxxxx.com --mode snapshot --storage vmxxxxx

101: May 09 00:00:02 INFO: Starting Backup of VM 101 (qemu)
101: May 09 00:00:02 INFO: status = running
101: May 09 00:00:02 INFO: unable to open file '/etc/pve/nodes/proxmox/qemu-server/101.conf.tmp.359369' - Device or resource busy
101: May 09 00:00:02 ERROR: Backup of VM 101 failed - command 'qm set 101 --lock backup' failed: exit code 2

 

[psauxw]

Looking at my NASs, its not a space problem ... if that helps a bit

edit: one of my node looks offline in the GUI but its online.
Trying to give as much details as i can.

 

[psauxw]

Restarting the pve-cluster ... i can't see my 2nd node anymore. Anyone?

 

[psauxw]

sorry for the thread spamming ....

Found the solution.... /etc/init.d/cman restart did the trick

I guess some sort of network failure could have caused the cluster issue hance blocking the vzdump ...

Could that be it? I remember some DNS problems yesterday.

 

[dietmar]

I guess some sort of network failure could have caused the cluster issue hance blocking the vzdump ...
Could that be it?

Yes, seems your cluster did not work correctly.