On Sat, Jan 12, 2013 at 12:03:16AM -, Dmitrijs Ledkovs wrote:
> Debian dropped clustered lvm2 support.
>* Drop cluster (clvm) support. It never properly worked and is more dead
> than alive.
> -- Bastian Blank Wed, 02 Jan 2013 11:11:41 +0100
It it certainly not dead upstream and d
Debian dropped clustered lvm2 support.
lvm2 (2.02.95-6) unstable; urgency=low
* Drop cluster (clvm) support. It never properly worked and is more dead
than alive.
-- Bastian Blank Wed, 02 Jan 2013 11:11:41 +0100
Do we still want it in Ubuntu?
--
You received this bug notification be
Sigh, I see, this (bug 833368) has been sitting awhile. In 10 days if
needed I'll propose a patch to make 'monitoring = 1' work.
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
--
You received this bug not
Thanks for that information.
As per discussion on irc, this is actually a bug in lvm2. You should be
able to set monitoring to on in lvm.conf. I will mark this bug against
lvm2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
The vg was created as a normal vg. Ie.
vgcreate vg2 /dev/disk/by-id/dm-uuid-mpath-.
Then I installed and configured clustering (cman, clvm, fence-agents)
and once cman was running I ran lvmconf --enable-cluster, vgchange -cy
vg2 and finally service clvm start.
At this point /etc/init.d/clvm c
Can you tell us exactly how you created the vg? Is it possible to work
around this through lvm.conf settings? (I didn't offhand see a way to
do so) If not, we'll need to work through upstream to add support for
this to src/storage/storage_backend_logical.c.
--
You received this bug notificatio
Thanks for reporting this bug.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
