Public bug reported:
Starting or autostarting a clustered lvm2 volumegroup fails with the
error below. Non-clustered vgs works as expected.
# virsh pool-start vg2
error: Failed to start pool vg2
error: internal error Child process (/sbin/vgchange -ay vg2) status unexpected:
exit status 5
# vgs vg2
VG #PV #LV #SN Attr VSize VFree
vg2 1 10 0 wz--nc 2.00t 1.76t
# /sbin/vgchange -ay vg2
activation/monitoring=0 is incompatible with clustered Volume Group "vg2":
Skipping.
# echo $?
5
A possible fix is that libvirt calls vgchange with "--monitor y" param:
# /sbin/vgchange -ay --monitor y vg2
10 logical volume(s) in volume group "vg2" now active
Additional information:
# lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04
# apt-cache policy libvirt-bin
libvirt-bin:
Installed: 0.9.8-2ubuntu17.4
Candidate: 0.9.8-2ubuntu17.4
# apt-cache policy lvm2
lvm2:
Installed: 2.02.66-4ubuntu7.1
Candidate: 2.02.66-4ubuntu7.1
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075950
Title:
Starting clustered lvm vg pool fails with status 5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1075950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
