VERITAS Storage Foundation 4.1 Cluster File System HP Serviceguard Storage Management Suite Extracts, December 2005

Appendix A, Troubleshooting and Recovery
Installation Issues
125
CFS Problems
If there is a device failure or controller failure to a device, the file system may become
disabled cluster-wide. To address the problem, unmount all secondary mounts, unmount
the primary, then run a full fsck. When the file system check completes, mount all nodes
again.
Unmount Failures
The umount command can fail for the following reasons:
◆ When unmounting shared file systems, you must unmount the secondaries before
unmounting the primary.
◆ A reference is being held by an NFS server. Unshare the mount point and try the
unmount again.
Mount Failures
Mounting a file system can fail for the following reasons:
◆ The file system is not using disk layout Version 4, 5 or 6.
◆ The mount options do not match the options of already mounted nodes.
◆ A cluster file system is mounted by default with the qio option enabled if the node
has a Quick I/O for Databases license installed, 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 qio option enabled. So if some nodes in the cluster have a Quick
I/O license installed and others do not, a cluster mount can succeed on some nodes
and fail on others due to different mount options. To avoid this situation, ensure that
Quick I/O licensing is uniformly applied, or be careful to mount the cluster file
system with the qio/noqio option appropriately specified on each node of the
cluster. See the mount(1M) manual page for more information on mount options.
◆ A shared CVM volume was not specified.
◆ The device is still mounted as a local file system somewhere on the cluster. Unmount
the device.
◆ The fsck or mkfs command is being run on the same volume from another node, or
the volume is mounted in non-cluster mode from another node.
◆ The vxfsckd daemon is not running. This typically happens only if the CFSfsckd
agent was not started correctly.