<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 17, 2009, at 10:27 AM, Romi Verma wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">ok let me explain it bit more.<br>i have configured lvm resource in cluster and it is running on node A . as expected the vg is active on node A<br><br>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.<br> <br>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.<br>i expected it to , exclusivly activate the VG during resource start up. (vgchange -a e )</blockquote><div><br></div><div>submit a patch for the RA to the heartbeat project?</div><br><blockquote type="cite">do we have some other Resource agent which exclusivly activate the VG during resource start up??</blockquote><div><br></div><div>why not just fix the script?</div><br><blockquote type="cite"><br><br><br><div class="gmail_quote">On Tue, Feb 17, 2009 at 2:40 PM, Andrew Beekhof <span dir="ltr"><<a href="mailto:beekhof@gmail.com">beekhof@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c"><br> On Feb 17, 2009, at 10:03 AM, Romi Verma wrote:<br> <br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi All,<br> i have just configured LVM resouce agent in pacemaker cluster. i am kind of suprised as it is not taking care of exclusive activation.<br> am i missing something or LVM Resouce agent is written in this way only. can anyone put some light here.<br> </blockquote> <br></div></div> You'll have to do better with the question first.<br> <br> By "exclusive activation" you mean that the cluster only starts it in one place?<br> <br> 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.<br> <br> But we'd need more than a vague question to be able to comment further.<br> <br> _______________________________________________<br> Pacemaker mailing list<br> <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br> </blockquote></div><br> _______________________________________________<br>Pacemaker mailing list<br><a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>http://oss.clusterlabs.org/mailman/listinfo/pacemaker<br></blockquote></div><br></body></html>