PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System)

6.6.1.2 Creating Fsystem Resources

Set up an Fsystem resource if you want to mount a file system when userApplication is started.
To control multiple mount points in parent-child relationships, create the file system as one Fsystem resource.
You need to work on the following prerequisites to create an Fsystem resource.

Mount point characteristics

• Mount points are used to mount UFS and other local file systems.
• The file system can be shared as an NFS file system in the network. The file system can also be set up so that it is not shared.
• When a file system is shared in the network, the NFS Lock Failover function becomes enabled.

Notes on using the file lock facility

If you use an application together with file lock processing, you should pay careful attention to the following. Even if you are not sure if an application uses file lock, you should nevertheless observe the following:

• On the node responsible for standby operation with NFS servers, do not use the NFS client function. Do not implement NFS mount.
• A file system in which NFS is shared with the standby operation of NFS servers must be used only from the NFS client. Do not use a file directly from an application on a node on which NFS servers are operating.
• When failover occurs, access from the client is temporarily delayed because the following processing is performed when statd or lockd is restarted:
  • Stopping the statd(1M) or lockd(1M) daemon
  • Starting the statd(1M) or lockd(1M) daemon
  • NFS lock recovery processing

  The above notes on the three items relate to the resynchronization of the file lock during NFS server takeover. When the file lock is resynchronized, all the locks that are under the management of NFS are released and regained.

Notes on using NFS

Protocols to be used

NFS uses the TCP and UDP protocols. If you execute failover and then failback by using TCP, the recovery time may become longer.

Creating 31 or more Fsystem resources

The minimum Timeout value of the Fsystem resource is determined by the formula " No. of Fsystem resources x 6 seconds".

The default timeout is 180 seconds. If you set 30 or more Fsystem resources, it is necessary to change Timeout to the proper value based on " No. of F system resources x 6 seconds" on the [Confirmation of registration information] screen.

---

6.6.1.2.1 Prerequisites

6.6.1.2.2 Setup Method