Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

Table B-2
Unique message identifiers and messages (continued)
Message and DefinitionMessage Number
UX:vxfs command: ERROR: V-3-20076: message
■ Description
The command called stat() on a file, which is usually a file system
mount point, but the call failed.
■ Action
Check that the path specified is what was intended and that the
user has permission to access that path.
20076
UX:vxfs command: ERROR: V-3-21256: message
■ Description
The attempt to mount the file system failed because either the
request was to mount a particular Storage Checkpoint that does
not exist, or the file system is managed by an HSM and the HSM
is not running.
■ Action
In the first case, use the fsckptadm list command to see which
Storage Checkpoints exist and mount the appropriate Storage
Checkpoint. In the second case, make sure the HSM is running. If
the HSM is not running, start and mount the file system again.
21256
UX:vxfs command: ERROR: V-3-21264: message
■ Description
The attempt to mount a VxFS file system has failed because either
the volume being mounted or the directory which is to bethe mount
point is busy.
The reason that a VxVM volume could be busy is if the volume is
in a shared disk group and the volume is currently being accessed
by a VxFS command, such as fsck, on a node in the cluster.
One reason that the mount point could be busy is if a process has
the directory open or has the directory as its current directory.
Another reason that the mount point could be busy is if the
directory is NFS-exported.
■ Action
For a busy mount point, if a process has the directory open or has
the directory as its current directory, use the fuser command to
locate the processes and either get them to release their references
to the directory or kill the processes. Afterward, attempt to mount
the file system again.
21264
187Diagnostic messages
Unique message identifiers