This is how we have setup.
1. xfs (mount fs here you might have ext3 file system)
2. exportfs (export your file system)
3. IP (virtual IP)
You start in this order and heartbeat will automatically stop in reverse order.
you might need to tune up your exportfs script which is located in
/usr/lib/ocf/resource.d/heartbeat/
I have script called nfsserver
I made modification on following code.
####################################################
#
# export_mount()
#
# Get the status of the NFS mount and return whether it shows up in the
etab or not
#
export_mount ()
{
ocf_log info "--------> Running export_mount ${OCF_RESKEY_export_path} $
{OCF_RESKEY_export_parameters}"
rc=0;
if grep "^${OCF_RESKEY_export_path}\b" /var/lib/nfs/etab; then
ocf_log info "${OCF_RESKEY_export_path} is already exported,
removing"
unexport_mount
$rc=$?
fi
if [ $rc -eq 0 ]; then
if [ -n "${OCF_RESKEY_export_parameters}" ] ; then
export_parameters="-o ${OCF_RESKEY_export_parameters}"
fi
ocf_log info "exportfs ${export_parameters} -v
\*:${OCF_RESKEY_export_path}"
exportfs ${export_parameters} -v \*:${OCF_RESKEY_export_path}
rc=$?
if [ $rc -ne 0 ] ; then
ocf_log err Failed to export ${OCF_RESKEY_export_path}:
return = $rc
fi
fi
return $rc
}
> From: [email protected]
> To: [email protected]
> Date: Wed, 30 Dec 2009 21:16:02 +0400
> Subject: [Linux-HA] nfs config - help needed
>
> Could you please guide me as how to configure NFS (heartbeat 2.1.3) for
> below situation.
>
> ****
>
> I have configred heartbeat with each one Virtual IP resource for each node
> and configured few lvm partitions for each node as per the requirement.
>
> Tested the failover of IP and lvm partitions, it is working fine.
>
> Now I want to configure NFS Server resource on nodeA and proper mount points
> - to be handled by heartbeat CRM.
>
> please advise me how I can achieve this?
>
>
>
>
>
> **Actual Situation****
>
> I have two node cluster - nodeA & nodeB. I have a NFS drive (/dev/sdb5)
> mounted
> & exported on nodeA as well as imported / mounted via nfs client on nodeB.
>
> In this situation, using heartbeat2, I want NFS to be available for failover
> condition. That is,
> when the nodeA goes down still /dev/sdb5 should be available for nodeB.
>
> /dev/sdb5 is shared drive from SAN configured and made available to both the
> nodes.
>
> In the normal (o/s level) NFS is configured and mounted on nodeA and nodeB
> and working fine.
>
> Now I want NFS to be configured on hearbeat as CRM resource and when nodeA
> goes down still the mount
> point mounted on nodeB available and working.
>
> how this can be achived?
>
> What are all the resources I have to configure on hb_gui?
>
> how I have to handle the mounts on nodeA & nodeB?
>
> how I have to handle the failver of NFS to nodeB?
>
>
> O/S - Suse Linux 10.2 / heartbeat 2.1.3 / crm
>
> thanks
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha See also:
> http://linux-ha.org/ReportingProblems
>
> _____
>
> Hotmail: Free, trusted and rich email service. Get it
> <http://clk.atdmt.com/GBL/go/171222984/direct/01/> now.
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
