[Pacemaker] drbd + lvm

[David Vossel]

----- Original Message -----
> From: "Infoomatic" <infoomatic at gmx.at>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Thursday, March 13, 2014 5:28:19 PM
> Subject: Re: [Pacemaker] drbd + lvm
> 
> > > Has anyone had this issue and resolved it? Any ideas? Thanks in advance!
> > 
> > Yep, i've hit this as well. Use the latest LVM agent. I already fixed all
> > of this.
> > 
> > https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/LVM
> > 
> > Keep your volume_list the way it is and use the 'exclusive=true' LVM
> > option.   This will allow the LVM agent to activate volumes that don't
> > exist in the volume_list.
> > 
> > Hope that helps
> 
> Thanks for the fast response. I upgraded LVM to the backports
> (2.02.95-4ubuntu1.1~precise1) and used this script, but I am getting errors
> when one of the nodes tries to activate the VG.
> 
> The log:
> Mar 13 23:21:03 lxc02 LVM[7235]: INFO: 0 logical volume(s) in volume group
> "replicated" now active
> Mar 13 23:21:03 lxc02 LVM[7235]: INFO: LVM Volume replicated is not available
> (stopped)
> 
> "exclusive" is true and the tag is "pacemaker". Someone got hints? tia!

Yeah, those aren't errors. It's just telling you that the LVM agent stopped successfully. I would expect to see these after you did a failover or resource recovery.

Is the resource not starting and stopping correctly for you? If not, I'll need more logs.

-- Vossel

> infoomatic
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>