<div dir="ltr">Hello,<div><br></div><div><div style="font-size:12.8px">Could you please share any links/steps to create NFS HA cluster over gfs2 file system using Pacemaker. <span style="font-size:12.8px">Currently
I have completed till mounting of gfs2 file systems on cluster nodes
and now I need to create cluster resources for NFS server, exports and
mount on client.</span><br></div></div><div style="font-size:12.8px"><span style="font-size:12.8px"><br></span></div><div style="font-size:12.8px"><span style="font-size:12.8px">I followed some RedHat forums and created NFS cluster resources<span style="color:rgb(255,0,0)"> </span></span><span style="font-family:arial,helvetica,sans-serif;font-size:small"><span style="color:rgb(255,0,0)">but still "showmount -e" doesn't list the export entries,</span> <br><br><b>[root@node1-emulex ~]# pcs status</b><br>Cluster name: mycluster<br>Stack: corosync<br>Current DC: node2-atto (version 1.1.15-11.el7_3.4-e174ec8) - partition with quorum<br>Last updated: Mon May 1 09:55:47 2017 Last change: Mon May 1 07:50:25 2017 by root via cibadmin on node1-emulex<br><br>2 nodes and 10 resources configured<br><br>Online: [ node1-emulex node2-atto ]<br><br>Full list of resources:<br><br> scsi (stonith:fence_scsi): Started node2-atto<br> Clone Set: dlm-clone [dlm]<br> Started: [ node1-emulex node2-atto ]<br> Clone Set: clvmd-clone [clvmd]<br> Started: [ node1-emulex node2-atto ]<br> Clone Set: clusterfs-clone [clusterfs]<br> Started: [ node1-emulex node2-atto ]<br> ClusterIP (ocf::heartbeat:IPaddr2): <wbr> Started node1-emulex<br> NFS-D (ocf::heartbeat:nfsserver): <wbr> Started node1-emulex<br> nfs-cm-shared (ocf::heartbeat:exportfs): <wbr> Started node2-atto<br><br>Daemon Status:<br> corosync: active/enabled<br> pacemaker: active/enabled<br> pcsd: active/enabled<br>[root@node1-emulex ~]#<br><span style="color:rgb(255,0,0)">[root@node1-emulex ~]# showmount -e 172.30.59.253<br>Export list for <a href="http://172.30.59.253" target="_blank">172.30.59.253</a>:<br>[root@node1-emulex ~]#</span><br><br></span><font size="2"><span style="font-family:arial,helvetica,sans-serif"><b>Note:</b> Below steps are followed to create nfs resources after mounting gfs2 file systems on cluster nodes <br></span></font><font size="2"><span style="font-family:arial,helvetica,sans-serif"><br>1. pcs resource create ClusterIP ocf:heartbeat:IPaddr2 ip=172.30.59.253 cidr_netmask=19 op monitor interval=30s<br>2. pcs resource create NFS-D nfsserver nfs_shared_infodir=/mnt/<wbr>pacemaker/nfsinfo nfs_ip=172.30.59.253</span></font><div><font size="2"><span style="font-family:arial,helvetica,sans-serif">3. pcs resource create nfs-cm-shared exportfs clientspec=<a href="http://192.168.2.0/255.255.255.0" target="_blank">172.30.59.254/255.2<wbr>55.224.0</a> options=rw,sync,no_root_squash directory=/mnt/pacemaker/<wbr>exports fsid=0<br></span></font></div><div><font size="2"><span style="font-family:arial,helvetica,sans-serif">4. Added resource dependancies<br>5. [root@node2-atto ~]# showmount -e 172.30.59.253<br>Export list for <a href="http://192.168.2.90" target="_blank">172.30.59.253</a>:<br></span></font></div><font size="2"><span style="font-family:arial,helvetica,sans-serif">**** No Entries *****</span></font></div><div style="font-size:12.8px"><span style="font-family:arial,helvetica,sans-serif;font-size:small"><br><b>[root@node1-emulex ~]# pcs status resources clusterfs-clone</b><br> Clone: clusterfs-clone<br> Meta Attrs: interleave=true<br> Resource: clusterfs (class=ocf provider=heartbeat type=Filesystem)<br> Attributes: device=/dev/volgroup/vol directory=/mnt/pacemaker/ fstype=gfs2 options=noatime,localflocks<br> Operations: start interval=0s timeout=60 (clusterfs-start-interval-0s)<br> stop interval=0s timeout=60 (clusterfs-stop-interval-0s)<br> monitor interval=10s on-fail=fence (clusterfs-monitor-interval-<wbr>10s)<br>[root@node1-emulex ~]#<br><b>[root@node1-emulex ~]# pcs status resources ClusterIP</b><br> Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)<br> Attributes: ip=172.30.59.253 cidr_netmask=19<br> Operations: start interval=0s timeout=20s (ClusterIP-start-interval-0s)<br> stop interval=0s timeout=20s (ClusterIP-stop-interval-0s)<br> monitor interval=30s (ClusterIP-monitor-interval-<wbr>30s)<br>[root@node1-emulex ~]#<br><b>[root@node1-emulex ~]# pcs status resources NFS-D</b><br> Resource: NFS-D (class=ocf provider=heartbeat type=nfsserver)<br> Attributes: nfs_shared_infodir=/mnt/<wbr>pacemaker/nfsinfo nfs_ip=172.30.59.253<br> Operations: start interval=0s timeout=40 (NFS-D-start-interval-0s)<br> stop interval=0s timeout=20s (NFS-D-stop-interval-0s)<br> monitor interval=10 timeout=20s (NFS-D-monitor-interval-10)<br>[root@node1-emulex ~]#<br><b>[root@node1-emulex ~]# pcs status resources nfs-cm-shared</b><br> Resource: nfs-cm-shared (class=ocf provider=heartbeat type=exportfs)<br> Attributes: clientspec=<a href="http://172.30.59.254/255.255.224.0" target="_blank">172.30.59.254/255.<wbr>255.224.0</a> options=rw,sync,no_root_squash directory=/mnt/pacemaker/<wbr>exports fsid=0<br> Operations: start interval=0s timeout=40 (nfs-cm-shared-start-interval-<wbr>0s)<br> stop interval=0s timeout=120 (nfs-cm-shared-stop-interval-<wbr>0s)<br> monitor interval=10 timeout=20 (nfs-cm-shared-monitor-<wbr>interval-10)<br><br></span></div><div style="font-size:12.8px"><span style="font-family:arial,helvetica,sans-serif;font-size:small"><b>Query:</b> </span><font size="2"><span style="font-family:arial,helvetica,sans-serif">I went through RedHat forums and it is mentioned that <span style="color:rgb(51,51,51);font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:22.5625px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">Exporting a GFS2 filesystem in an Active/Active configuration is only supported when using <b>Samba+CTDB</b>
to export the GFS2 filesystem. Please let us know if its mandatory to
configure CTDB when nfs over gfs2 is configured or anyother options is
available.<br><br></span></span></font></div><div style="font-size:12.8px"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(51,51,51);font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:22.5625px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">Thanks,<br></span></span></font></div><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(51,51,51);font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:22.5625px;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);display:inline;float:none">Munavar.</span></span></font></div><div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #d3d4de">
<tr>
<td style="width:55px;padding-top:13px"><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank" style="color:#4453ea">www.avg.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>
<br>
<p style="text-align:justify"><span lang="EN-US"><font size="1">DISCLAIMER</font></span></p>
<p style="text-align:justify"><font size="1"><span lang="EN-US">The information in this e-mail is confidential and may be subject to
legal privilege. It is intended solely for the addressee. Access to this e-mail
by anyone else is unauthorized. If you have received this communication in
error, please address with the subject heading "Received in error,"
send to <a href="mailto:it@msystechnologies.com" target="_blank">it@msystechnologies.com</a>,
then delete the e-mail and destroy any copies of it. If you are not the
intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful.
The views, opinions, conclusions and other information expressed in this
electronic mail and any attachments are not given or endorsed by the company
unless otherwise indicated by an authorized representative independent of this
message.</span></font></p>
<font size="1"><span lang="EN-US">MSys cannot guarantee
that e-mail communications are secure or error-free, as information could be
intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or
contain viruses, though </span>all reasonable
precautions have been taken to ensure no viruses are present in this e-mail<span lang="EN-US">. </span>As our company cannot accept responsibility for
any loss or damage arising from the use of this e-mail or attachments we
recommend that you subject these to your virus checking procedures prior to use</font>