Mounting a file system can fail for the following reasons:
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.
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.
vxfsckd
daemon is not running. This typically happens only if the CFSfsckd
agent was not started correctly.
mount
fails with an error message:
vxfs mount: cannot open mnttab
/etc/mnttab
is missing or you do not have root
privileges.
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.
The node may be in the process of joining the cluster.
-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