Troubleshooting
Cluster File System Problems
mount: slow
The node may be in the process of joining the cluster.
•If you try to mount a file system that is already mounted onto another cluster node, without the
#mount -F vxfs /dev/vx/dsk/share/vol01 /vol01
The following error message displays:
vxfs mount: /dev/vx/dsk/share/vol01 is already mounted, /vol01 is busy, allowable number of mount points exceeded, or cluster reservation failed for the volume
Command Failures
•Manual pages not accessible with the man command. Set the MANPATH environment variable to include the path to the Veritas manual pages.
•The mount, fsck, and mkfs utilities reserve a shared volume. They fail on volumes that are in use. Be careful when accessing shared volumes with other utilities such as dd, it is possible for these commands to destroy data on the disk.
•Running some commands, such as vxupgrade
vxfs vxupgrade: ERROR: not primary in a cluster file system
This means that you can run this command only on the primary, that is, the system that mounted this file system first.
Performance Issues
Quick I/O File system performance is adversely affected if a cluster file system is mounted with the qio option enabled and Quick I/O is licensed, but the file system is not used for Quick I/O files. Because qio is enabled by default, if you do not intend to use a shared file system for Quick I/O, explicitly specify the noqio option when mounting.
High Availability Issues
Low Memory
Under heavy loads, software that manages heartbeat communication links may not be able to allocate kernel memory. If this occurs, a node halts to avoid any chance of network partitioning. Reduce the load on the node if this happens frequently.
A similar situation may occur if the values in the /etc/llttab files on all cluster nodes are not correct or identical.
Appendix A | 51 |