<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
<blockquote type="cite"
cite="mid:CALuPYL3cuccWb98iKT_toDAP+oYYwoUFtiXs4qgNTMgL5LGwmQ@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div><i><span>"I noticed you didn't configure LVM resource agent
to manage your VG's (de)activation task,</span><br>
<span>not sure if it can always work as expect, so have more
exceptional checking :)"</span><br>
</i></div>
<div><br>
</div>
<div> Strangely the Pacemaker active-passive
configuration example shows VG controlled by Pacemaker, while
the active-active one does not. I have taken the active-active
configuration for Pacemaker and created 2 LVs, then instead of
formatting it using the GFS2 clustered filesystem, I used
normal XFS and made sure that it is mounted only on one node
at a time. (lv01 on node 2, lv02 on node2)</div>
<div><br>
</div>
<div> <a
href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/global_file_system_2/ch-clustsetup-gfs2"
moz-do-not-send="true">https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/global_file_system_2/ch-clustsetup-gfs2</a></div>
<div><br>
</div>
<div> I can see the clustered VG and LVs as soon <span>ocf:heartbeat:clvm
is started.</span></div>
<div><br>
</div>
<div>Is there anything I am missing here?</div>
</div>
</blockquote>
<br>
Good. "clvm" will activate all VGs by default. If you have more than
one VG in your cluster, you may want to<br>
activate/deactivate one VG for each group of "vg" and "xfs", then
you may need to look at LVM for each VG:<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/LVM">https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/LVM</a><br>
<br>
Eric<br>
</body>
</html>