[Pacemaker] how to mount drive on SAN with pacemaker resource agent?

[Mike Diehn]

To make sure the failed server is actually dead, you want to use STONITH.
 So read about that.  Here are examples from our testing cluster.  These are
broken, so don't use them as they are.  That's why they are set to "Stopped"
right now.  I probably have some timing stuff very wrong:


primitive ShootLebekmfs1 stonith:external/ipmi \
        meta target-role="Stopped" \
        params hostname="lebekmfs1" ipaddr="10.1.1.59" userid="stonith"
passwd="ShootMeInTheHead" interface="lan"
primitive ShootLebekmfs2 stonith:external/ipmi \
        meta target-role="Stopped" \
        params hostname="lebekmfs2" ipaddr="10.1.1.61" userid="stonith"
passwd="ShootMeInTheHead" interface="lan"


You can use the ocf:heartbeat:Filesystem resource to mount any file system
you can mount manually.  Here's one from a config in our test cluster.  This
works:

primitive lvTest ocf:heartbeat:Filesystem \
        params device="/dev/EkmCluVG/lvTest" directory="/srv/test1"
fstype="ocfs2" \
        op monitor interval="10s" timeout="10s"


Make sure you remove the file system from your /etc/fstab if you're going to
do it this way.  During testing, for my convenience, I leave it in, but add
the noauto option to prevent it being mounted on boot.

Best,
Mike

On Tue, Jan 4, 2011 at 2:05 PM, Michael Hittesdorf <
michael.hittesdorf at chicagotrading.com> wrote:

>  Can I use the Filesystem resource agent to mount a SAN drive in the event
> of a failover? How do I ensure that the failed server no longer has the
> drive mounted so as to prevent storage corruption? Having read several of
> the tutorials, I’m aware of DRBD and the clustered file systems GFS2 and
> OCFS2.  However, I don’t need simultaneous access to the disk from both of
> my cluster nodes. I just want to make the shared SAN storage available to
> the primary, active server only as my cluster is active-passive.  Is there a
> recommended way to accomplish this?
>
>
>
> Thanks for your help!
>
> This message is intended only for the personal and confidential use of the
> recipients named above. If the reader of this email is not the intended
> recipient, you have received this email in error and any review,
> dissemination, distribution or copying is strictly prohibited. If you have
> received this email in error, please notify the sender immediately by return
> email and permanently delete the copy you received. This message is provided
> for informational purposes and should not be construed as a solicitation or
> offer to buy or sell any securities or related financial instruments.Neither CTC Holdings nor any affiliates (CTC) are responsible for any
> recommendation, solicitation, offer or agreement or any information about
> any transaction, customer account or account activity that may be attached
> to or contained in this communication. CTC accepts no liability for any
> content contained in the email, or any errors or omissions arising as a
> result of e-mail transmission. Any opinions contained in this email
> constitute the sender's best judgment at this time and are subject to change
> without notice. CTC London Limited is authorized and regulated by the
> Financial Services Authority.
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>


-- 
Mike Diehn
Senior Systems Administrator
ANSYS, Inc - Lebanon, NH Office
mike.diehn at ansys.com, (603) 727-5492
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110104/ec7dd6f2/attachment-0002.htm>