Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 failed

[planet-itservices]

Hey there,

we have an problem with our backups.
On the Proxmox Hosts are 4 machines (two Win2008R2 and two Debian 7.0) which should be backup'd with vzdump, mode snapshot on an iSCSI target.
One of the machines is running the backups fine, the other ones not.

This is in the Log:

INFO: starting new backup job: vzdump 103 104 105 --quiet 1 --mailto xxxx@ourdomain.com --mode snapshot --compress lzo --storage  Snapshots --node vmhost
INFO: Starting Backup of VM 103 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: suspend vm to make snapshot
INFO:   Logical volume "vzsnap-vmhost-0" created
INFO: trying to remove stale snapshot '/dev/win2008r2/vzsnap-vmhost-1'
INFO: lvremove failed - trying again in 8 seconds
INFO: lvremove failed - trying again in 16 seconds
INFO: lvremove failed - trying again in 32 seconds
ERROR: command 'lvremove -f /dev/win2008r2/vzsnap-vmhost-1' failed: exit code 5
INFO:   device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 failed: Device or resource busy
INFO:   Aborting. Failed to activate snapshot exception store.
INFO: lvremove failed - trying again in 8 seconds
INFO: lvremove failed - trying again in 16 seconds
INFO: lvremove failed - trying again in 32 seconds
ERROR: command 'lvremove -f /dev/win2008r2/vzsnap-vmhost-1' failed: exit code 5
INFO: resume vm
INFO: vm is online again after 131 seconds
ERROR:  Backup of VM 103 failed - command 'lvcreate --size 1024M --snapshot  --name 'vzsnap-vmhost-1' '/dev/win2008r2/vm-103-disk-2'' failed: exit  code 5

At first I thought its a problem with the Guest OS but QM 103 is an Debian Machine. QM 104 is an Win2008R2 Machine and the Backup is fine. QM 105 is an Debian 7.0 again and the backups getting the same Error like QM 103.

I don't get why the first Debian is able to be backup'd and the second is not?

Thanks in advance,

So Far Planet-ITservices

 

[tom]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

you are using an outdated version. for more info about the current KVM backup system, see http://pve.proxmox.com/wiki/Backup_and_Restore

 

[planet-itservices]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

Yeah I know that Proxmox 2.2 is an outdated Version
We would like to upgrade to 3.0 but for this task it would be nice to have backups of the machines so we could restore them in case of an error.
And the really strange behavoir is, we had the backups working like 3 weeks ago. And from one day to another it stopped working... But we didn't change any configuration?

 

[dietmar]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

Try to remove the the snapshot manually:

# lvremove -f /dev/win2008r2/vzsnap-vmhost-1

Does that work?

 

[planet-itservices]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

With the manually command I get the following error:

root@vmhost:~# lvremove -f /dev/win2008r2/vzsnap-vmhost-1
One or more specified logical volume(s) not found.

So this is strange, vzdump can't remove the Snapshot because it's not present? Why I get an Error then?

 

[dietmar]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

So this is strange, vzdump can't remove the Snapshot because it's not present? Why I get an Error then?

Maybe some kind of timeout or a race condition. Does it work now, or does the problem show up again?

 

[planet-itservices]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

I didn't try a Backup yet, the normal planned backups are going to run up on saturday night.
I was just wondering why the backup was fine for a long time on all machines and suddenly stopped working on some machines.

 

[planet-itservices]

Re: Backup failed with device-mapper: create ioctl on win2008r2-vzsnap--vmhost--1 fai

Hey Guys,

we coudldn't find a solution for our problem. Even after removeing the vzsnap-vmhost-1 manually (rm -rf) the error occured at every backup time.
So we really like to update to Proxmox 3.0 but without valid i can't update the system...