RE: NFS clustering - how to use fsid= options for theexports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a simliar setup, but I just set a Service to manage the IP address and filesystems. It's not that difficult to manage two /etc/exports files...  

________________________________

From: linux-cluster-bounces@xxxxxxxxxx on behalf of Finnur Örn Guðmundsson - TM Software
Sent: Thu 2/7/2008 12:24 PM
To: linux-cluster@xxxxxxxxxx
Subject:  NFS clustering - how to use fsid= options for theexports



Hi,

 

I have setup a active-standby NFS cluster.

 

Everything is working like it should, except for one thing.

 

In HP ServiceGuard you use /etc/exports on each node in a active-standby cluster to manage exports, and there you can use the fsid=X for each filesystem you want to export (helps with stale nfs errors after a failover).

 

In RHCS i cannot seem to get the server to correctly use the options ...

 

Here is my service:

 

                <service autostart="1" domain="nfsdomain" name="nfs">

                        <nfsexport name="home1">

                                <nfsclient name="nfshome" options="rw,sync,fsid=150" path="/home" target="10.50.102.128/25"/>

                                <nfsclient name="nfsdata" options="rw,fsid=50,sync" path="/data" target="10.50.102.128/25"/>

                                <clusterfs ref="home"/>

                                <ip ref="10.10.10.10"/>

                                <clusterfs ref="data"/>

                        </nfsexport>

 

Would this not be the correct way ? Is there a other way to do this except for manually using /etc/exports and just have RHCS manage the IP address transfer beteween the nodes?

 

Kær kveðja / Best Regards,

Finnur Örn Guðmundsson
Network Engineer - Network Operations
fog@xxxx <mailto:fog@xxxx> 

TM Software
Urðarhvarf 6, IS-203 Kópavogur, Iceland
Tel: +354 545 3000 - fax +354 545 3610
www.tm-software.is <http://www.tm-software.is/> 

This e-mail message and any attachments are confidential and may be privileged. TM Software e-mail disclaimer: www.tm-software.is/disclaimer <http://www.tm-software.is/disclaimer>  




-----------------------------------------
This message is intended only for the individual or entity to which
it is addressed and contains information that is proprietary to The
Babcock & Wilcox Company and/or its affiliates, or may be otherwise
confidential.  If the reader of this message is not the intended
recipient, or the employee agent responsible for delivering the
message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in
error, please notify the sender immediately by return e-mail and
delete this message from your computer.  Thank you.

<<winmail.dat>>

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux