mode failure - unable to detect lvm volume group

D

darkpixel

Renowned Member
Oct 26, 2010
31
9
73
About a week ago I did my usual 'apt-get update && apt-get dist-upgrade' on one of my Proxmox machines and rebooted.

Now the nightly backup is suspending the VM rather than doing a snapshot.
Other than installing the updates, the box hasn't seen changes in several months.

I missed the problem in the logs the first night, so I upgraded the rest of the servers in my cluster. Now they are suffering from the same issue.

All the virtual machines use iscsi for storage.

Version info and backup logs:

kvm3:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-50
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-50
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6
kvm3:~#

kvm3:~# uname -a
Linux kvm3 2.6.32-6-pve #1 SMP Fri Nov 4 06:54:05 CET 2011 x86_64 GNU/Linux
kvm3:~#




vzdump --quiet --node 6 --snapshot --compress --storage virtsnaps --maxfiles 3 --mailto email-address-redacted@example.tld 106


106: Nov 30 02:30:02 INFO: Starting Backup of VM 106 (qemu)
106: Nov 30 02:30:02 INFO: running
106: Nov 30 02:30:02 INFO: status = running
106: Nov 30 02:30:02 INFO: mode failure - unable to detect lvm volume group
106: Nov 30 02:30:02 INFO: trying 'suspend' mode instead
106: Nov 30 02:30:02 INFO: backup mode: suspend
106: Nov 30 02:30:02 INFO: ionice priority: 7
106: Nov 30 02:30:02 INFO: suspend vm
106: Nov 30 02:30:03 INFO: creating archive '/mnt/pve/virtsnaps/vzdump-qemu-106-2011_11_30-02_30_02.tgz'
106: Nov 30 02:30:03 INFO: adding '/mnt/pve/virtsnaps/vzdump-qemu-106-2011_11_30-02_30_02.tmp/qemu-server.conf' to archive ('qemu-server.conf')
106: Nov 30 02:30:03 INFO: adding '/dev/disk/by-id/scsi-14945540000000000bc92943370c0328e590cad7cef84c294' to archive ('vm-disk-virtio0.raw')
106: Nov 30 02:52:25 INFO: Total bytes written: 13618599424 (9.68 MiB/s)
106: Nov 30 02:52:26 INFO: archive file size: 6.06GB
106: Nov 30 02:52:27 INFO: resume vm
106: Nov 30 02:52:27 INFO: vm is online again after 1345 seconds
106: Nov 30 02:52:27 INFO: Finished Backup of VM 106 (00:22:25)

[edit: pasted log was formatted poorly]
 
analyse your lvm setup.

> lvs

> lvdisplay
 
Seems you use an iscsi device directly (/dev/disk/by-id/scsi-14945540000000000bc92943370c0328e590cad7cef84c294)

Snapshot never worked for such configuration!
 
tom said:
analyse your lvm setup.

> lvs

> lvdisplay
Click to expand...

kvm3:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-ao 166.33G
root pve -wi-ao 58.00G
swap pve -wi-ao 4.00G
kvm3:~# lvdisplay
--- Logical volume ---
LV Name /dev/pve/swap
VG Name pve
LV UUID g5edN1-eR2X-QOxk-UjxV-Wk80-40Yk-T1LDeu
LV Write Access read/write
LV Status available
# open 1
LV Size 4.00 GB
Current LE 1024
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/pve/root
VG Name pve
LV UUID gJcBqK-W0An-wGfs-qDOx-YIJQ-VcWq-Bk1dWa
LV Write Access read/write
LV Status available
# open 1
LV Size 58.00 GB
Current LE 14848
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name /dev/pve/data
VG Name pve
LV UUID rogDVp-bODA-tXuU-O36X-DXns-fHGy-thLEuB
LV Write Access read/write
LV Status available
# open 1
LV Size 166.33 GB
Current LE 42581
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

kvm3:~#
 
dietmar said:
Seems you use an iscsi device directly (/dev/disk/by-id/scsi-14945540000000000bc92943370c0328e590cad7cef84c294)

Snapshot never worked for such configuration!
Click to expand...

It's working at 3 different sites right now--just not the one I apt-get dist-upgraded.
 
darkpixel said:
It's working at 3 different sites right now--just not the one I apt-get dist-upgraded.
Click to expand...

I stand corrected. I dredged up old logs from my problem site from a month ago--the VMs are suspending.

I find it funny that a 24/7 outfit that has its servers regularly suspending for several hours at a time hasn't made a peep...
 
darkpixel said:
It's working at 3 different sites right now--just not the one I apt-get dist-upgraded.
Click to expand...

It is impossible that this setup works with snapshots (and it has never worked). Making such false claims is confusing and a big wast of time.
 
You must log in or register to reply here.
Top Bottom