Symantec logo

Unique message identifiers

Some commonly encountered UMIs and the associated messages are described on the following table:

Unique message identifiers and messages

Message Number

Message and Definition

20002 

UX:vxfs command: ERROR: V-3-20002: message 

  • Description

    The command attempted to call stat() on a device path to ensure that the path refers to a character device before opening the device, but the stat() call failed. The error message will include the platform-specific message for the particular error that was encountered, such as "Access denied" or "No such file or directory".

  • Action

    The corrective action depends on the particular error.

20003 

UX:vxfs command: ERROR: V-3-20003: message 

  • Description

    The command attempted to open a disk device, but the open() call failed. The error message includes the platform-specific message for the particular error that was encountered, such as "Access denied" or "No such file or directory".

  • Action

    The corrective action depends on the particular error.

20005 

UX:vxfs command: ERROR: V-3-20005: message 

  • Description

    The command attempted to read the superblock from a device, but the read() call failed. The error message will include the platform-specific message for the particular error that was encountered, such as "Access denied" or "No such file or directory".

  • Action

    The corrective action depends on the particular error.

20012 

UX:vxfs command: ERROR: V-3-20012: message 

  • Description

    The command was invoked on a device that did not contain a valid VxFS file system.

  • Action

    Check that the path specified is what was intended.

20076 

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.

21256 

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.

21264 

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 be the 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.

    If the directory is NFS-exported, unexport the directory, such as by using unshare mntpt on the Solaris operating system. Afterward, attempt to mount the file system again.

21268 

UX:vxfs command: ERROR: V-3-21268: message 

  • Description

    This message is printed by two different commands: fsckpt_restore and mount. In both cases, the kernel's attempt to mount the file system failed because of I/O errors or corruption of the VxFS metadata.

  • Action

    Check the console log for I/O errors and fix any problems reported there. Run a full fsck.

21272 

UX:vxfs command: ERROR: V-3-21272: message 

  • Description

    The mount options specified contain mutually-exclusive options, or in the case of a remount, the new mount options differed from the existing mount options in a way that is not allowed to change in a remount.

  • Action

    Change the requested mount options so that they are all mutually compatible and retry the mount.

23729 

UX:vxfs command: ERROR: V-3-23729: message 

  • Description

    Cluster mounts require the vxfsckd daemon to be running, which is controlled by VCS.

  • Action

    Check the VCS status to see why this service is not running. After starting the daemon via VCS, try the mount again.

24996 

UX:vxfs command: ERROR: V-3-24996: message 

  • Description

    In some releases of VxFS, before the VxFS mount command attempts to mount a file system, mount tries to read the VxFS superblock to determine the disk layout version of the file system being mounted so that mount can check if that disk layout version is supported by the installed release of VxFS. If the attempt to read the superblock fails for any reason, this message is displayed. This message will usually be preceded by another error message that gives more information as to why the superblock could not be read.

  • Action

    The corrective action depends on the preceding error, if any.