[Pacemaker] exclusive activation of Volume Group

[Romi Verma]

ok let me explain it bit more.
i have configured lvm resource in cluster and it is running on node A . as
expected the vg is active on node A

but from node B , if  i do vgchange -a y <vgname> , it becomes active on
node B also .and this is not affecting the lvm resource. lvm resource is
running fine on node A  as if nothing happend.

i saw the lvm resource agent code . it is using only vgchange -a y <vgname>
during resource start up and due to this it is happening.
i expected it to , exclusivly activate the VG during resource start up.
(vgchange -a e )

do we have some other Resource agent which exclusivly activate the VG during
resource start up??


On Tue, Feb 17, 2009 at 2:40 PM, Andrew Beekhof <beekhof at gmail.com> wrote:

>
> On Feb 17, 2009, at 10:03 AM, Romi Verma wrote:
>
>  Hi All,
>> i have just configured LVM resouce agent in pacemaker cluster.  i am kind
>> of suprised as it is not taking care of exclusive activation.
>> am i missing something or LVM Resouce agent is written in this way only.
>> can anyone put some light here.
>>
>
> You'll have to do better with the question first.
>
> By "exclusive activation" you mean that the cluster only starts it in one
> place?
>
> The cluster goes to great lengths to ensure this and (except for cloned
> resources) normally when resources "appear" to be active on multiple nodes
> either the script is broken or the admin has configured the nodes to start
> it at boot.
>
> But we'd need more than a vague question to be able to comment further.
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20090217/6c640d28/attachment-0001.html>