scnas: NAS Filesystem did not get Mounted During Bootup (6268260)

Problem Summary: The NFS file system cannot be checked for viability prior to a failover or scswitch being used to locate the data service to the node. If a node doesn't have the NFS filesystem, a switch/failover to that node will result in a failure of the data service that requires manual intervention. A mechanism like HAStoragePlus is needed to check the viability of the filesystem prior to attempting the fail/switchover to that node.

Workaround: File systems using NAS filers (with entries in /etc/vfstab) are mounted outside Sun Cluster software control, and this means that Sun Cluster software is unaware of any problems. Should the file system become unavailable, some data services, such as Sun Cluster HA for Oracle, will fail when data service methods, such as START or STOP, are executed.

Failure of these methods may lead to several possibilities:

• The data services resource, such as HA-Oracle, may go into the STOP_FAILED state, if the application (Oracle) binaries are not available.

• The data service may continuously attempt to fail over to alternate nodes until it is able to start successfully or startup attempts have failed on all possible nodes.

Perform one of the following procedures to avoid the above problems:

• Place the application binaries on either a failover or cluster file system. Then configure a HAStoragePlus resource to represent this file system and record a dependency of the application upon this resource. The system will not attempt to start the application when the file system is not available.

• Place the application binaries on the local root file system. If the local root file system does not work, the node will not be able to join the cluster, and the system will not attempt to start the application on that node.