Problems with snapshot backups

  • Thread starter Thread starter SirLouen
  • Start date Start date
S

SirLouen

Guest
I cannot manage to do backups lately. I feel this has something to do with the logical volumen system uses for snapshot

proxmoxsrv:/# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
datalv datavg owi-ao 930.51G
vzsnap-proxmoxsrv-0 datavg Swi-Io 1.00G datalv 100.00
data pve owi-ao 47.53G
root pve -wi-ao 18.50G
swap pve -wi-ao 7.00G
vzsnap-proxmoxsrv-0 pve swi-ao 1.00G data 0.37

Here is the error in the log:

102: Jan 04 14:18:01 INFO: Starting Backup of VM 102 (qemu)
102: Jan 04 14:18:01 INFO: running
102: Jan 04 14:18:01 INFO: status = running
102: Jan 04 14:18:01 INFO: backup mode: snapshot
102: Jan 04 14:18:01 INFO: ionice priority: 7
102: Jan 04 14:18:01 INFO: trying to remove stale snapshot '/dev/datavg/vzsnap-proxmoxsrv-0'
102: Jan 04 14:18:01 INFO: umount: /mnt/vzsnap0: device is busy
102: Jan 04 14:18:01 INFO: umount: /mnt/vzsnap0: device is busy
102: Jan 04 14:18:01 INFO: umount: /mnt/vzsnap0: device is busy
102: Jan 04 14:18:01 ERROR: command 'umount /mnt/vzsnap0' failed with exit code 1
102: Jan 04 14:18:02 INFO: /dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
102: Jan 04 14:18:02 INFO: Can't remove open logical volume "vzsnap-proxmoxsrv-0"
102: Jan 04 14:18:02 ERROR: command 'lvremove -f '/dev/datavg/vzsnap-proxmoxsrv-0'' failed with exit code 5
102: Jan 04 14:18:02 INFO: /dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
102: Jan 04 14:18:02 INFO: Logical volume "vzsnap-proxmoxsrv-0" already exists in volume group "datavg"
102: Jan 04 14:18:02 INFO: /dev/dm-4: read failed after 0 of 4096 at 0: Input/output error
102: Jan 04 14:18:02 INFO: Can't remove open logical volume "vzsnap-proxmoxsrv-0"
102: Jan 04 14:18:02 ERROR: command 'lvremove -f '/dev/datavg/vzsnap-proxmoxsrv-0'' failed with exit code 5
102: Jan 04 14:18:02 ERROR: Backup of VM 102 failed - command 'lvcreate --size 1024M --snapshot --name 'vzsnap-proxmoxsrv-0' '/dev/datavg/datalv'' failed with exit code 5

Can't figure out with it is busy. I did killall the vzsnap process successfully.

Any ideas of what might be happening?
 
I think i've found the problem

I have one VM that has two disks virtio1 and virtio2.

In viritio1 is installed the OS, windows 2008 100gb
In virtio2, is stored big amounts of data, 1Tb

The backup disk is 2Tb big, but the VM takes tooo long to get backuped with snapshot method >5 hours, because of the amount of data in virtio2

It is possible to backup just virtio1 from that VM ?
 
Hi, with recent (I think >= 1.6) proxmox you can do it, but not from web interface.
In any case man qm explains it (option [,backup=yes|no] related to storage).

Es. exclude ide0 and ide1:
(just edit your /etc/qemu-server/VMID.conf):
...
ide0: local:136/vm-136-disk-1.raw,backup=no
ide1: /dev/sdc1,backup=no
...
 
This worked for me. But I've found that also backup fails for some reason and found this errors in the log:

Jan 19 12:01:33 kernel usb 2-4: USB disconnect, address 14
Jan 19 12:01:33 NetworkManager <debug> [1295434893.283576] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/volume_uuid_9645aaf7_2aaf_4af4_9a3b_569a03d2efde').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.305436] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/storage_serial_Seagate_Desktop_2GHLH2WB_0_0').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.307336] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0_scsi_host_0_scsi_device_lun0').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.307367] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0_scsi_host_0').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.312317] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0_scsi_host').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.316854] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0').
Jan 19 12:01:33 NetworkManager <debug> [1295434893.321478] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB').
Jan 19 12:01:45 kernel usb 2-4: new high speed USB device using ehci_hcd and address 15
Jan 19 12:01:45 kernel scsi906 : usb-storage 2-4:1.0
Jan 19 12:01:45 NetworkManager <debug> [1295434905.731138] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB').
Jan 19 12:01:45 NetworkManager <debug> [1295434905.779468] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0').
Jan 19 12:01:45 NetworkManager <debug> [1295434905.782732] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0_scsi_host').

USB connects and disconnects constantly, during a backup, and while idle. Don't know exactly why, this did not happen me in the proxmox 1.5 but in proxmox 1.6 and after started to happen for some reason constantly... any ideas regardng this issue?
 
SirLouen said:
Jan 19 12:01:45 NetworkManager <debug> [1295434905.782732] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_bc2_3300_2GHLH2WB_if0_scsi_host').
Click to expand...

You run NetworkManager on a pve host?!
 
just remove the network-manager!? (aptitude remove network-manager)
 
Ok, I did that and now:

Jan 21 12:33:04 kernel usb 2-4: USB disconnect, address 56
Jan 21 12:33:16 kernel usb 2-4: new high speed USB device using ehci_hcd and address 57
Jan 21 12:33:16 kernel scsi66 : usb-storage 2-4:1.0
Jan 21 12:33:17 kernel scsi 66:0:0:0: Direct-Access Seagate Desktop 0130 PQ: 0 ANSI: 4

Same thing but with no info of network-manager basically about the removal. Why usb keeps disconnecting and connecting constantly? usb problems with proxmox machines?
$ pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.7-9
pve-kernel-2.6.35-1-pve: 2.6.35-9
pve-kernel-2.6.32-3-pve: 2.6.32-14
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4


Regards!
 
ok, I am confused now. network-manager and usb are just two different topics.
 
I read somewhere that
Since it said: new high speed USB device using ehci_hcd and address 15

I should try
# modprobe -r ehci_hcd
FATAL: Module ehci_hcd not found

No success :(
 
Here is an answer I saw somewhere in the internet:

Those errors arise because your system loads uhci-hcd before ehci-hcd.
You can change the load order to get rid of the errors, or you can just
ignore them.

Here's what happens. When uhci-hcd loads, the USB core sees your
high-speed hub and begins to initialize it. A few moments later ehci-hcd
loads, and it switches the port connection away from the UHCI controller
over to the EHCI controller. As a result uhci-hcd isn't able to
communicate with the hub any more -- that's what the error messages are
reporting. But ehci-hcd is able to communicate with it perfectly well
Click to expand...

But I can't interprt... what I'm supposed to do based on this? where is the place where I config the module loading order?
 
You must log in or register to reply here.
Top Bottom