Backup problem

T

Tallaril

New Member
Feb 18, 2011
23
0
1
Hi there,

i have a strange problem with VM machines backup on all nodes.

I've configured a automated backup at night. At backup start, the node says:

INFO: starting new backup job: vzdump 202 --quiet 1 --mode snapshot --node bazinga-2 --compress 0 --maxfiles 1 --storage backup01
INFO: Starting Backup of VM 202 (qemu)
INFO: status = running
INFO: mode failure - unable to detect lvm volume group
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: suspend vm


The VM is running fine within the LVM volume group ... is there any reason why this happens? I mean, a susoend for 5 minutes is not a problem, but this takes hours ......


 
Last edited:
provide details about your LVM setup - did you install from our ISO?
 
tom said:
provide details about your LVM setup - did you install from our ISO?
Click to expand...

i've installed it through package ... it is a fresh squeeze system with 3 nodes. All 3 have it's own LVM volume group which name is the same as thenodes name.

i have swap, home and root configured and the rest as free lvm space.

the vm is running in LVM and this works fine ....

Which information do you need?
 
Code: 
lvdisplay

pvdisplay

df -h
 
INFO: starting new backup job: vzdump 103 --mode snapshot --compress 1 --storage nfs-230-76 --node server1
INFO: Starting Backup of VM 103 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: trying to remove stale snapshot '/dev/pve/vzsnap-server1-0'
INFO: umount: /mnt/vzsnap0: not mounted
ERROR: command ''umount /mnt/vzsnap0'' failed: exit code 1
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-server1-0' failed: Not a CODE reference at /usr/share/perl5/PVE/Tools.pm line 352.
INFO: /dev/pve/vzsnap-server1-0: read failed after 0 of 4096 at 215687823360: Input/output error
INFO: /dev/pve/vzsnap-server1-0: read failed after 0 of 4096 at 215687880704: Input/output error
INFO: /dev/pve/vzsnap-server1-0: read failed after 0 of 4096 at 0: Input/output error
INFO: /dev/pve/vzsnap-server1-0: read failed after 0 of 4096 at 4096: Input/output error
INFO: /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
INFO: /dev/sdd: read failed after 0 of 4096 at 1429720727552: Input/output error
INFO: /dev/sdd: read failed after 0 of 4096 at 1429720784896: Input/output error
INFO: /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
INFO: Logical volume "vzsnap-server1-0" already exists in volume group "pve"
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-server1-0' failed: Not a CODE reference at /usr/share/perl5/PVE/Tools.pm line 352.
ERROR: Backup of VM 103 failed - command ''lvcreate --size 1024M --snapshot --name '\''vzsnap-server1-0'\'' '\''/dev/pve/data'\'' failed: exit code 5
INFO: Backup job finished with errors
TASK ERROR: job errors
 
ok, let's start:

Node 1:

lvdisplay
--- Logical volume ---
LV Name /dev/bazinga/root
VG Name bazinga
LV UUID mdjcgr-2Hdy-ioAe-27tw-iJTn-3MH0-6vuyoQ
LV Write Access read/write
LV Status available
# open 1
LV Size 9,31 GiB
Current LE 2384
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/bazinga/swap_1
VG Name bazinga
LV UUID 5ybQ2z-SGJ4-Wo9U-It5B-ZHmL-9IEP-Ceh3dn
LV Write Access read/write
LV Status available
# open 1
LV Size 15,27 GiB
Current LE 3908
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name /dev/bazinga/home
VG Name bazinga
LV UUID cKVXNv-sJJl-m1Kd-v71Z-MTeV-xu9k-66qt4Y
LV Write Access read/write
LV Status available
# open 1
LV Size 400,00 GiB
Current LE 102400
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/bazinga/vm-110-disk-1
VG Name bazinga
LV UUID x3Ge8W-DYFs-u2sO-LtP5-15fC-FZNq-zHUZiF
LV Write Access read/write
LV Status available
# open 1
LV Size 60,00 GiB
Current LE 15360
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3

--- Logical volume ---
LV Name /dev/bazinga/vm-112-disk-1
VG Name bazinga
LV UUID yD5TGf-lT4w-cCZK-ZL3n-givB-Omfs-jVCqkx
LV Write Access read/write
LV Status available
# open 1
LV Size 60,00 GiB
Current LE 15361
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

# pvdisplay --- Physical volume ---
PV Name /dev/sda5
VG Name bazinga
PV Size 1,36 TiB / not usable 3,00 MiB
Allocatable yes
PE Size 4,00 MiB
Total PE 357558
Free PE 218145
Allocated PE 139413
PV UUID Z2YqjQ-6CZS-RafU-FzgG-Yl0w-DTp8-Hapv8D

# df -h
Dateisystem Size Used Avail Use% Eingehängt auf
/dev/mapper/bazinga-root
9,2G 1,2G 7,6G 14% /
tmpfs 3,9G 0 3,9G 0% /lib/init/rw
udev 3,9G 256K 3,9G 1% /dev
tmpfs 3,9G 44M 3,9G 2% /dev/shm
/dev/sda1 228M 33M 184M 16% /boot
/dev/fuse 30M 32K 30M 1% /etc/pve
backup.fserver.org:/home/swen/slux/bazinga
917G 721G 149G 83% /media/backup/bazinga
/dev/mapper/bazinga-home
394G 390M 374G 1% /home



Node 2: Master

# lvdisplay
--- Logical volume ---
LV Name /dev/bazinga-2/root
VG Name bazinga-2
LV UUID 1cln8J-AfsI-PtSS-QBvF-aG1U-aORU-5PgHV8
LV Write Access read/write
LV Status available
# open 1
LV Size 9,31 GiB
Current LE 2384
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/bazinga-2/swap_1
VG Name bazinga-2
LV UUID Hue1zv-dE02-Orvt-zDpo-Nv7W-TBjn-zDS15M
LV Write Access read/write
LV Status available
# open 1
LV Size 15,27 GiB
Current LE 3908
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name /dev/bazinga-2/home
VG Name bazinga-2
LV UUID WkqSEj-QSWb-VO1U-v7h9-UuFx-PjUn-WhprKM
LV Write Access read/write
LV Status available
# open 1
LV Size 30,00 GiB
Current LE 7680
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/bazinga-2/vm-200-disk-1
VG Name bazinga-2
LV UUID swh0xL-3UkZ-tWul-DFMR-dUFx-EwCP-fPxPAC
LV Write Access read/write
LV Status available
# open 1
LV Size 32,00 GiB
Current LE 8193
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3

--- Logical volume ---
LV Name /dev/bazinga-2/vm-201-disk-1
VG Name bazinga-2
LV UUID mkNJuL-wHiT-8R3t-YJcZ-PSW5-uWx4-yFTNYE
LV Write Access read/write
LV Status available
# open 1
LV Size 32,01 GiB
Current LE 8194
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

--- Logical volume ---
LV Name /dev/bazinga-2/vm-100-disk-1
VG Name bazinga-2
LV UUID YcwK6i-g3Ai-idf3-WW82-2OH0-qDIo-xIMLOy
LV Write Access read/write
LV Status available
# open 1
LV Size 40,00 GiB
Current LE 10240
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5

--- Logical volume ---
LV Name /dev/bazinga-2/vm-202-disk-1
VG Name bazinga-2
LV UUID G7JFWL-oiQn-qy8I-BE0B-aKu8-YiB5-8YnuzV
LV Write Access read/write
LV Status available
# open 1
LV Size 32,00 GiB
Current LE 8193
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6

--- Logical volume ---
LV Name /dev/bazinga-2/vm-106-disk-1
VG Name bazinga-2
LV UUID QxTPB5-QmSF-dQwz-2Qnl-vjoT-qpxE-Or8tfS
LV Write Access read/write
LV Status available
# open 1
LV Size 50,00 GiB
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:7


# pvdisplay
--- Physical volume ---
PV Name /dev/sda5
VG Name bazinga-2
PV Size 931,07 GiB / not usable 2,00 MiB
Allocatable yes
PE Size 4,00 MiB
Total PE 238354
Free PE 176762
Allocated PE 61592
PV UUID gMY2Z6-17U1-pAf4-CLie-LcDJ-NYVJ-wHcj3C

# df -h
Dateisystem Size Used Avail Use% Eingehängt auf
/dev/mapper/bazinga--2-root
9,2G 1,8G 7,0G 21% /
tmpfs 3,9G 0 3,9G 0% /lib/init/rw
udev 3,9G 256K 3,9G 1% /dev
tmpfs 3,9G 41M 3,9G 2% /dev/shm
/dev/sda1 228M 33M 184M 15% /boot
/dev/mapper/bazinga--2-home
30G 364M 28G 2% /home
/dev/fuse 30M 32K 30M 1% /etc/pve
 
I Got the same problem.

--- Physical volume ---
PV Name /dev/md1
VG Name vg0
PV Size 698.39 GiB / not usable 3.94 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 178786
Free PE 0
Allocated PE 178786
PV UUID X9vKPG-SX3z-dHfb-ZgNJ-OyqM-XJwq-6sbQuj

PV VG Fmt Attr PSize PFree
/dev/md0 --- 0 0
/dev/md1 vg0 lvm2 a-- 698.38g 0
/dev/ram0 --- 0 0
/dev/ram1 --- 0 0
/dev/ram10 --- 0 0
/dev/ram11 --- 0 0
/dev/ram12 --- 0 0
/dev/ram13 --- 0 0
/dev/ram14 --- 0 0
/dev/ram15 --- 0 0
/dev/ram2 --- 0 0
/dev/ram3 --- 0 0
/dev/ram4 --- 0 0
/dev/ram5 --- 0 0
/dev/ram6 --- 0 0
/dev/ram7 --- 0 0
/dev/ram8 --- 0 0
/dev/ram9 --- 0 0
/dev/root --- 0 0
/dev/vg0/home --- 0 0
/dev/vg0/swap --- 0 0
/dev/vg0/tmp --- 0 0
/dev/vg0/var --- 0 0

--- Physical volume ---
PV Name /dev/md1
VG Name vg0
PV Size 698.39 GiB / not usable 3.94 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 178786
Free PE 0
Allocated PE 178786
PV UUID X9vKPG-SX3z-dHfb-ZgNJ-OyqM-XJwq-6sbQuj



Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-root 35G 894M 33G 3% /
tmpfs 3.9G 0 3.9G 0% /lib/init/rw
udev 3.9G 240K 3.9G 1% /dev
tmpfs 3.9G 19M 3.9G 1% /dev/shm
/dev/md0 247M 40M 195M 17% /boot
/dev/mapper/vg0-home 75G 25G 47G 35% /home
/dev/mapper/vg0-tmp 15G 166M 14G 2% /tmp
/dev/mapper/vg0-var 553G 55G 471G 11% /var
/dev/fuse 30M 16K 30M 1% /etc/pve
 
AFAIK is this problem related to debian and lvm. Search for "lvremove snapshot"
I remember there was a tip to install the hal-package: apt-get install hal
I don't have a problem until now.

Dirk
 
results of fuser /dev/pve/vzsnap-server1-0 is? I am thinking that there is a hung process holding the file handle open.

 
You know what? I missed your post! Tragic, because you're right, hal packet solved it! Thanks! You're my hero of the month!
 
You must log in or register to reply here.
Top Bottom
Back