ERROR: command 'umount /mnt/vzsnap0' failed with exit code 1

Danielc1234

Active Member
Jan 10, 2010
82
0
26
Hi All. I just had to remount our NAS drive in order to create some vzdump/backups.

I just ran a backup for one of our VM-101 and in the log file of the backup I got this line that has the error 'ERROR: command 'umount /mnt/vzsnap0' failed with exit code 1'.

Although I was sent a email stating the the backup was successful, can this be confirmed that it is backup up properly? We haven't have any backup on our servers for a while now and really need for this to work.

Just would like some confirmation that this is in deed working.

Code:
Nov 26 08:38:01 INFO: Starting Backup of VM 101 (qemu)
Nov 26 08:38:01 INFO: running
Nov 26 08:38:01 INFO: status = running
Nov 26 08:38:02 INFO: backup mode: snapshot
Nov 26 08:38:02 INFO: ionice priority: 7
Nov 26 08:38:02 INFO: trying to remove stale snapshot '/dev/pve/vzsnap-ourserver-0'
Nov 26 08:38:02 INFO: umount: /mnt/vzsnap0: not mounted
Nov 26 08:38:02 ERROR: command 'umount /mnt/vzsnap0' failed with exit code 1
Nov 26 08:38:02 INFO:   /dev/dm-5: read failed after 0 of 4096 at 0: Input/output error
Nov 26 08:38:02 INFO:   Logical volume "vzsnap-ourserver-0" successfully removed
Nov 26 08:38:13 INFO:   Logical volume "vzsnap-ourserver-0" created
Nov 26 08:38:13 INFO: creating archive '/mnt/pve/NAS-Backup/vzdump-qemu-101-2011_11_26-08_38_01.tar'
Nov 26 08:38:13 INFO: adding '/mnt/pve/NAS-Backup/vzdump-qemu-101-2011_11_26-08_38_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
Nov 26 08:38:13 INFO: adding '/mnt/vzsnap0/images/101/vm-101-disk-1.raw' to archive ('vm-disk-ide0.raw')
Nov 26 10:34:56 INFO: Total bytes written: 66911751680 (9.11 MiB/s)
Nov 26 10:34:56 INFO: archive file size: 62.32GB
Nov 26 10:34:56 INFO: delete old backup '/mnt/pve/NAS-Backup/vzdump-qemu-101-2011_10_04-02_01_41.tgz'
Nov 26 10:35:24 INFO:   Logical volume "vzsnap-ourserver-0" successfully removed
Nov 26 10:35:24 INFO: Finished Backup of VM 101 (01:57:23)
 
there was some old snapshot. looks not bad, but in ANY case, test your backups regularly by doing test restores. this is a general rule for all backups.
 
Dear All,
I also had error when the schedule backup run, fail without any backup file created.
I used to work, it just had been failed this last few weeks.
Please help.
Thanks before.

Below is the code:
INFO: starting new backup job: vzdump 100 --quiet 1 --mode snapshot --compress lzo --storage backup
INFO: Starting Backup of VM 100 (openvz)
INFO: CTID 100 exist mounted running
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: trying to remove stale snapshot '/dev/pve/vzsnap-proxmox-0'
INFO: umount: /mnt/vzsnap0: not mounted
ERROR: command 'umount /mnt/vzsnap0' failed: exit code 1
INFO: Logical volume "vzsnap-proxmox-0" successfully removed
INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-proxmox-0')
INFO: Logical volume "vzsnap-proxmox-0" created
INFO: creating archive '/backup/dump/vzdump-openvz-100-2013_11_26-05_00_02.tar.lzo'
INFO: lzop: No space left on device: <stdout>
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/pve/vzsnap-proxmox-0' failed: exit code 5
ERROR: Backup of VM 100 failed - command '(cd /mnt/vzsnap0/private/100;find . '(' -regex '^\.$' ')' -o '(' -type 's' -prune ')' -o -print0|sed 's/\\/\\\\/g'|tar cpf - --totals --sparse --numeric-owner --no-recursion --one-file-system --null -T -|lzop) >/backup/dump/vzdump-openvz-100-2013_11_26-05_00_02.tar.dat' failed: exit code 1
INFO: Backup job finished with errors
TASK ERROR: job errors
 
Thanks Dietmar,
It used to work automatically by removing the old backup file, and then create the latest backup file, which i want the way it works.
Backup space is 50GB, and i choose to have 2 (now it is 17GB each file) backup files only on the storage.
Otherwise, i need to manually move the the backup file to free some space for the schedule backup job run well, which i DON'T WANT the way it works.
Please advise.
Thanks.

Best regards,
Edy
 
just to note, if you still use 1.x you should upgrade to latest version - 1.x is EOL since a long time.