NOTE: Remove remote shell permissions after completing the CFS installation and configuration.
Resource Temporarily Unavailable
If the installation fails with the following error message on the console:
fork() failed: Resource temporarily unavailable
The value of the nkthread tunable parameter may not be large enough. The nkthread tunable requires a minimum value of 600 on all systems in the cluster. To determine the current value of nkthread, enter:
#kctune –q nkthread
If necessary, you can change the value of nkthread using the System Management Homepage (SMH) tool, or by running the kctune command. If you change the value of nkthread, the kernel must be rebuilt for the new value to take effect. It is easier to change the value using SAM because there is an option to process the new kernel immediately. See the kctune(1M) manual pages for more information on tuning kernel parameters.
Inaccessible System
The system you specified is not accessible. This could be for a variety of reasons such as, the system name was entered incorrectly, or the system is not available over the network.
Checking communication with system01 | FAILED |
System not accessible : system01 |
|
Suggested solution: Verify that you entered the system name correctly; use the ping(1M) command to verify accessibility of the host.If a system cannot access the software source depot, either swagentd is not running on the target system or the swlist command cannot see the source depot.
Correct /etc/{hosts, nsswitch.conf} and continue from here Continue? [Y/N] :
Suggested solutions: check that swagentd is running. Check whether there is an entry for the target system in /etc/hosts. If there is no entry, then ensure the hosts file is not the primary lookup for the “hosts” entry in the /etc/nsswitch.conf file.
CFS Troubleshooting
If there is a device failure or controller failure to a device, the file system may become disabled
Unmount Failures
The umount command can fail if a reference is being held by an NFS server. Unshare the mount point and try to unmount again.
Mount Failures
Mounting a file system can fail for the following reasons:
•The file system is not using disk layout Version 6 or 7.
•The mount options do not match the options for already mounted nodes.
•If the node has a Quick I/O for Databases license installed, a cluster file system is mounted by default with the qio option enabled - even if the qio mount option was not explicitly specified. If the Quick I/O license is not installed, a cluster file system is mounted without the
10 Overview
