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.
•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
•The vxfsckd daemon is not running. This typically happens only if the CFSfsckd agent was not started correctly.
•If mount fails with the error message: vxfs mount: cannot open mnttab
/etc/mnttab is missing or you do not have root privileges.
•If mount fails with the error message:
vxfs mount: device already mounted, ...
The device is in use by mount, mkfs or fsck on the same node. This error cannot be generated from another node in the cluster.
•If the error message displays: 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.
CFS Troubleshooting 11