[PVE-User] lvremove failed - trying again in XX seconds
Laurent CARON
lcaron at unix-scripts.info
Fri Feb 24 12:14:17 CET 2012
Hi,
I'm sorry to heavily insist but I believe there is a bug (or maybe a
misunderstanding on my side) with vzdump/snapshots/lvm backups on 1.9.
I'm constantly getting "lvremove failed" while using snapshot backups.
My setup:
4 proxmox boxes (1.9):
# pveversion --verbose
pve-manager: 2.0-28 (pve-manager/2.0/30bb4d33)
running kernel: 2.6.32-7-pve
proxmox-ve-2.6.32: 2.0-60
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-22
qemu-server: 2.0-17
pve-firmware: 1.0-15
libpve-common-perl: 1.0-14
libpve-access-control: 1.0-11
libpve-storage-perl: 2.0-11
vncterm: 1.0-2
vzctl: 3.0.30-2pve1
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-3
ksm-control-daemon: 1.1-1
root FS is on softraid. This is *only* the root FS.
# cat /proc/mdstat
md0 : active raid1 sda1[0] sdb1[1]
31254336 blocks [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
# mount | grep pve
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
filer-002:/mnt/vg_md2/backups_proxmox/export on /mnt/pve/backups_tmm type nfs (rw,vers=3,addr=192.168.0.64)
# cat 701.conf
boot: dcn
bootdisk: ide0
cores: 1
ide0: LUN_lcaron:vm-701-disk-1
ide2: local:iso/grml64_2011.05.iso,media=cdrom
memory: 2048
name: vm-lc
net0: e1000=12:C1:3B:28:55:3B,bridge=vmbr0
ostype: l26
sockets: 1
# lvdisplay
--- Logical volume ---
LV Name /dev/VG_FAS-2040-SIEGE-LCARON/vm-701-disk-1
VG Name VG_FAS-2040-SIEGE-LCARON
LV UUID XjqsmN-MGVL-JD5F-79ST-6LvI-YdLn-7otcGw
LV Write Access read/write
LV Status NOT available
LV Size 32.00 GiB
Current LE 8192
Segments 1
Allocation inherit
Read ahead sectors auto
# iscsiadm --mode node
10.100.0.10:3260,2002 iqn.1992-08.com.netapp:sn.142254160
# vzdump --mode snapshot --mailto admin-proxmox at lncsa.fr --all 1 --node proxmox-vty-001 --maxfiles 2 --storage backups_tmm
INFO: starting new backup job: vzdump --mailto admin-proxmox at lncsa.fr --mode snapshot --maxfiles 2 --storage backups_tmm --node proxmox-vty-001 --all 1
INFO: Starting Backup of VM 701 (qemu)
INFO: status = running
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: Logical volume "vzsnap-proxmox-vty-001-0" created
INFO: creating archive '/mnt/pve/backups_tmm/dump/vzdump-qemu-701-2012_02_24-11_41_25.tar'
INFO: adding '/mnt/pve/backups_tmm/dump/vzdump-qemu-701-2012_02_24-11_41_25.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/dev/VG_FAS-2040-SIEGE-LCARON/vzsnap-proxmox-vty-001-0' to archive ('vm-disk-ide0.raw')
INFO: Total bytes written: 34359740928 (34.17 MiB/s)
INFO: archive file size: 32.00GB
INFO: delete old backup '/mnt/pve/backups_tmm/dump/vzdump-qemu-701-2012_02_21-12_45_02.tar.lzo'
INFO: lvremove failed - trying again in 8 seconds
INFO: lvremove failed - trying again in 16 seconds
INFO: lvremove failed - trying again in 32 seconds
INFO: Finished Backup of VM 701 (00:16:35)
INFO: Backup job finished successfully
The only way out is then a reboot of the host.
Suspend works well (just the VM is unavailable during backups).
The exact same setup works fine under ProxMox 1.8 (with kernel 2.6.35).
Regards,
Laurent
More information about the pve-user
mailing list