Veritas Storage Foundation 5.1 SP1 Cluster File System Installation Guide (5900-1510, April 2011)

■ If mount fails with an 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 this 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 without -o cluster
option (that is, not in shared mode) on another cluster node,
# 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
This section describes command failures.
■ Manual pages not accessible with the man command. Set the MANPATH
environment variable appropriately.
See “Setting environment variables” on page 32.
■ 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 -n 7 /vol02, can generate the
following error message:
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.
Troubleshooting information
Storage Foundation Cluster File System problems
450