Backup of VM failed - error: rbd: failed to create snapshot:

[vispa]

Hi,

I wonder if anyone can help.

I have backups scheduled every night and most of them seem to fail with this following error :-

INFO: starting new backup job: vzdump 102 --compress lzo --node cloud3 --mode snapshot --remove 0 --storage VispaNAS
INFO: Starting Backup of VM 102 (lxc)
INFO: status = running
INFO: CT Name: test.vispa.net.uk
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
snapshot create failed: starting cleanup
no lock found trying to remove 'backup'  lock
ERROR: Backup of VM 102 failed - rbd snapshot 'vm-102-disk-1' error: rbd: failed to create snapshot: (17) File exists
INFO: Backup job finished with errors
TASK ERROR: job errors

If I manually remove the backup, it seems to work fine for a few days and then the error happens again?

Can anyone throw any light on why this might be happening?

Regards,

James

 

[Alwin]

ERROR: Backup of VM 102 failed - rbd snapshot 'vm-102-disk-1' error: rbd: failed to create snapshot: (17) File exists

Please also check the '/var/log/ceph' logs, there should be more to find.

 

[vispa]

Hi,

I am still having this issue. Any help would be appreciated.

I have found a few people discuss this error on the web. Is it a bug with Proxmox?

INFO: found old vzdump snapshot (force removal)
rbd: sysfs write failed
can't unmap rbd device /dev/rbd/ceph-vm/vm-149-disk-1@vzdump: rbd: sysfs write failed
INFO: backup mode: snapshot

It seems the old snapshot can't be removed?

 

[sb-jw]

Try to stop the VM and unlock the RBD image and / or unmount the RBD device if mounted. If possible try to reboot the node, this might be solve this issue.

 

[vispa]

Hi,

rbd snap rm ceph-vm/vm-102-disk-1@vzdump

Actually solves the issue, but the backups are scheduled overnight and I end up with exactly the same error after a couple of nights.

 

[vispa]

Can anyone throw any light on this please as I'm actually considering moving away from Proxmox as we can't backup CT's

 

[nttec]

Is anyone able to solve this? I am experiencing this in one of my containers, the rest of the containers are able to create a backup and only one is now creating a backup as it should be. it keeps saying that file exist even there is no backup or snapshots created.

error: rbd: failed to create snapshot: (17) File exists

 

[MoreDakka]

I also am having this exact error. I'm on an older proxmox but it's been happening for months now.

Virtual Environment 5.4-3

INFO: Starting Backup of VM 105 (lxc)
INFO: status = running
INFO: CT Name: NAME
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
snapshot create failed: starting cleanup
no lock found trying to remove 'backup' lock
ERROR: Backup of VM 105 failed - rbd snapshot 'vm-105-disk-0' error: rbd: failed to create snapshot: (17) File exists
INFO: Backup job finished with errors

I would shut down the CT or VM, remove the snapshot, then within 2-4 days it would start erroring again..,.