ERROR: Backup of VM failed ... exit code 32

Discussion in 'Proxmox VE: Installation and configuration' started by mlanner, Aug 29, 2018.

  1. mlanner

    mlanner Member

    Joined:
    Apr 1, 2009
    Messages:
    181
    Likes Received:
    1
    I have an LXC container running on a Ceph pool. It's running just fine. It has a nightly backup set up to run. For the last week or so, the backup keeps on failing with:

    Code:
    vzdump 60180 --mailnotification always --mode snapshot --mailto someone@example.com --quiet 1 --storage nas01-backup-7x --compress lzo
    
    60180: 2018-08-29 01:00:02 INFO: Starting Backup of VM 60180 (lxc)
    60180: 2018-08-29 01:00:02 INFO: status = running
    60180: 2018-08-29 01:00:02 INFO: CT Name: my-lxc-container
    60180: 2018-08-29 01:00:02 INFO: found old vzdump snapshot (force removal)
    60180: 2018-08-29 01:00:02 INFO: backup mode: snapshot
    60180: 2018-08-29 01:00:02 INFO: ionice priority: 7
    60180: 2018-08-29 01:00:02 INFO: create storage snapshot 'vzdump'
    60180: 2018-08-29 01:00:03 ERROR: Backup of VM 60180 failed - command 'mount -o ro,noload /dev/rbd2 /mnt/vzsnap0//' failed: exit code 32
    
    If I list snapshots of that container, I can see a snapshot left behind.

    Code:
    # rbd --pool ceph snap ls vm-60180-disk-1
    SNAPID NAME       SIZE TIMESTAMP
        63 vzdump 65536 MB Wed Aug 29 01:00:03 2018
    
    Even if I clean up the snapshot with:

    Code:
    # rbd snap rm ceph/vm-60180-disk-1@vzdump
    
    ... it doesn't help.

    If I run a manual backup to the same storage backend, a NAS, but a different mount point, it generally works. I'm a bit baffled as to why this is failing.

    Anyone have any suggestions or ideas for why this is failing?
     
  2. GPLExpert

    GPLExpert New Member
    Proxmox VE Subscriber

    Joined:
    Jul 18, 2016
    Messages:
    12
    Likes Received:
    0
    Hello,

    I have the same problem an no solution too since 2 weeks with one container.
     
  3. mlanner

    mlanner Member

    Joined:
    Apr 1, 2009
    Messages:
    181
    Likes Received:
    1
    BUMP ... No one has a solution for this? If I shut down the container and back it up manually, I can get a backup to work. However, that's really not a great way to go about it.
     
  4. Jonathan Thompson

    Jonathan Thompson New Member

    Joined:
    Dec 30, 2018
    Messages:
    2
    Likes Received:
    0
    BUMP! I'm getting this too. LXC container on Ceph storage.

    Code:
    INFO: starting new backup job: vzdump 101 --node vmhost12 --remove 0 --compress lzo --storage local --mode snapshot
    INFO: Starting Backup of VM 101 (lxc)
    INFO: status = running
    INFO: CT Name: Unifi-Controller
    INFO: found old vzdump snapshot (force removal)
    rbd: sysfs write failed
    can't unmap rbd device /dev/rbd/Share/vm-101-disk-0@vzdump: rbd: sysfs write failed
    INFO: backup mode: snapshot
    INFO: ionice priority: 7
    INFO: create storage snapshot 'vzdump'
    mount: /dev/rbd4 is already mounted or /mnt/vzsnap0 busy
    umount: /mnt/vzsnap0/: not mounted
    command 'umount -l -d /mnt/vzsnap0/' failed: exit code 32
    ERROR: Backup of VM 101 failed - command 'mount -o ro,noload /dev/rbd4 /mnt/vzsnap0//' failed: exit code 32
    INFO: Backup job finished with errors
    TASK ERROR: job errors
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice