Proxmox KVM backup failed

I

itconstruct

Active Member
Aug 3, 2009
77
0
26
VMIDNAMESTATUSTIMESIZEFILENAME
110MAC-SWS8-1FAILED02:42:24command '(tar cvpf - -C '/mnt/vzsnap/images/110' --totals --sparse --numeric-owner --ignore-failed-read qemu-server.conf vm-110-disk-1.qcow2 vm-110-disk.qcow2|cstream -t 10485760 >/backup/vzdump-110.dat)' failed with exit code 2
TOTAL02:42:240KB

Detailed backup logs:

vzdump --quiet --snapshot --dumpdir /backup --mailto admin@itconstruct.com.au 110
110: Nov 11 14:00:01 INFO: Starting Backup of VM 110 (qemu)
110: Nov 11 14:00:02 INFO: status = running
110: Nov 11 14:00:02 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap')
110: Nov 11 14:00:03 INFO: Logical volume "vzsnap" created
110: Nov 11 14:00:03 INFO: mounting lvm snapshot
110: Nov 11 14:00:04 INFO: creating archive '/backup/vzdump-110.dat' (/mnt/vzsnap/images/110)
110: Nov 11 14:00:04 INFO: qemu-server.conf
110: Nov 11 14:00:04 INFO: vm-110-disk-1.qcow2
110: Nov 11 15:18:10 INFO: tar: vm-110-disk-1.qcow2: File shrank by 58493878272 bytes; padding with zeros
110: Nov 11 16:39:59 INFO: 100612685824 B 93.7 GB 9595.5 s (2:39 h) 10485361 B/s 10.00 MB/s
110: Nov 11 16:39:59 INFO: write: No space left on device
110: Nov 11 16:40:00 INFO: Logical volume "vzsnap" successfully removed
110: Nov 11 16:42:25 ERROR: Backup of VM 110 failed - command '(tar cvpf - -C '/mnt/vzsnap/images/110' --totals --sparse --numeric-owner --ignore-failed-read qemu-server.conf vm-110-disk-1.qcow2 vm-110-disk.qcow2|cstream -t 10485760 >/backup/vzdump-110.dat)' failed with exit code 2

This is the emailed log on the error.

Please advise.

I believe it is due to space running out on the backup location. Is it possible to add another hdd to the machine just for the backup directory? Is there a tutorial I can follow to adding an internal connected hard disk

Also how do I add a windows location to use for windows iso files for kvm?
 
itconstruct said:
VMIDNAMESTATUSTIMESIZEFILENAME
110MAC-SWS8-1FAILED02:42:24command '(tar cvpf - -C '/mnt/vzsnap/images/110' --totals --sparse --numeric-owner --ignore-failed-read qemu-server.conf vm-110-disk-1.qcow2 vm-110-disk.qcow2|cstream -t 10485760 >/backup/vzdump-110.dat)' failed with exit code 2
TOTAL02:42:240KB

Detailed backup logs:

vzdump --quiet --snapshot --dumpdir /backup --mailto admin@itconstruct.com.au 110
110: Nov 11 14:00:01 INFO: Starting Backup of VM 110 (qemu)
110: Nov 11 14:00:02 INFO: status = running
110: Nov 11 14:00:02 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap')
110: Nov 11 14:00:03 INFO: Logical volume "vzsnap" created
110: Nov 11 14:00:03 INFO: mounting lvm snapshot
110: Nov 11 14:00:04 INFO: creating archive '/backup/vzdump-110.dat' (/mnt/vzsnap/images/110)
110: Nov 11 14:00:04 INFO: qemu-server.conf
110: Nov 11 14:00:04 INFO: vm-110-disk-1.qcow2
110: Nov 11 15:18:10 INFO: tar: vm-110-disk-1.qcow2: File shrank by 58493878272 bytes; padding with zeros
110: Nov 11 16:39:59 INFO: 100612685824 B 93.7 GB 9595.5 s (2:39 h) 10485361 B/s 10.00 MB/s
110: Nov 11 16:39:59 INFO: write: No space left on device
110: Nov 11 16:40:00 INFO: Logical volume "vzsnap" successfully removed
110: Nov 11 16:42:25 ERROR: Backup of VM 110 failed - command '(tar cvpf - -C '/mnt/vzsnap/images/110' --totals --sparse --numeric-owner --ignore-failed-read qemu-server.conf vm-110-disk-1.qcow2 vm-110-disk.qcow2|cstream -t 10485760 >/backup/vzdump-110.dat)' failed with exit code 2

This is the emailed log on the error.

Please advise.

I believe it is due to space running out on the backup location. Is it possible to add another hdd to the machine just for the backup directory? Is there a tutorial I can follow to adding an internal connected hard disk

Also how do I add a windows location to use for windows iso files for kvm?
Click to expand...

the error log is clear: 'No space left on device'

take a look here:
http://pve.proxmox.com/wiki/Backup_-_Restore_-_Live_Migration

and for the samba mount:
http://pve.proxmox.com/wiki/Storage_Model
 
Thanks Tom.

that seemed to have worked however now both of the samba mounts(windows dir) are showing as enabled but not active.

When I try and browse these through the web console I receive the following error:

Code: 
[B]Internal Server Error[/B]

The server encountered an internal error or misconfiguration and was unable to complete your request. 

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error. 
[6648]ERR: 24: Error in Perl code: mkdir /mnt/iso1: File exists at /usr/share/perl5/PVE/Storage.pm line 2104 
     
Apache Embperl 2.2.0 [Sun Nov 15 16:06:50 2009]

The web console at the moment when viewing any of the storage pages takes forever to load.

How can I make them active again and keep them active?? How do I make this permanent regardless of whether the proxmox machine or the server that the drive is mounted from is rebooted??

Please advise.
 
itconstruct said:
Thanks Tom.

that seemed to have worked however now both of the samba mounts(windows dir) are showing as enabled but not active.

When I try and browse these through the web console I receive the following error:

Code: 
[B]Internal Server Error[/B]

The server encountered an internal error or misconfiguration and was unable to complete your request. 

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error. 
[6648]ERR: 24: Error in Perl code: mkdir /mnt/iso1: File exists at /usr/share/perl5/PVE/Storage.pm line 2104 
     
Apache Embperl 2.2.0 [Sun Nov 15 16:06:50 2009]
The web console at the moment when viewing any of the storage pages takes forever to load.

How can I make them active again and keep them active?? How do I make this permanent regardless of whether the proxmox machine or the server that the drive is mounted from is rebooted??

Please advise.
Click to expand...

what did you do exactly? pls post the content of your /etc/fstab file.
 
Code: 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
/dev/sda1 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
//mac-wamm-1/iso /mnt/iso1 cifs username=proxmox,password=PASSWORD_REMOVED,domain=itconstruct.internal 0 0
//mac-wamm-1/proxmox/backups /mnt/samba1 cifs username=proxmox,password=PASSWORD_REMOVED,domain=itconstruct.internal 0 0

That is the /etc/fstab file.

I have removed the passwords from the file and replaced that section with PASSWORD_REMOVED to show where the passwords where.

The steps I followed where from the link you provided me with - http://pve.proxmox.com/wiki/Storage_Model

Let me know if you need anything else.
 
dietmar said:
try

# umount /mnt/iso1

or reboot if nothing else helps.
Click to expand...

Hey Dietmar, thanks for your help so far.

This has worked for one of the mounts but the other shows the following error:

Code: 
proxmox:/mnt# mount /mnt/samba1
mount error: mount point /mnt/samba1 does not exist
proxmox:/mnt# umount /mnt/samba1
unmount error 16 = Device or resource busy
Refer to the umount.cifs(8) manual page (man 8 umount.cifs)

Does this mean I am required to reboot to fix this error?

I don't really want to have to reboot my proxmox machine every time thatthe internet drops off temporarily to get these back up!
 
Does this mean I am required to reboot to fix this error?

I don't really want to have to reboot my proxmox machine every time thatthe internet drops off temporarily to get these back up!
Click to expand...

Find out why the "Device or resource busy"? Still using some files?

It is never a good idea to simply turn off a file server while some hosts still mount shares.
 
dietmar said:
Find out why the "Device or resource busy"? Still using some files?

It is never a good idea to simply turn off a file server while some hosts still mount shares.
Click to expand...

No that is very true.

It does have one backup job specified that shuld run when the mounts are up on that /mnt/samba1 mount. However that one backup job is specified to run on a wednesday.

I don't know why this mount is currently being accessed from the proxmox machine as there are no jobs being run on it.

I did just notice that in the web console under storage it does specify that this mount is 89.69 GB when it should display the same size as the iso1 mount as 465.75 GB instead.

Please advise.
 
You must log in or register to reply here.
Top Bottom