VERITAS Volume Manager 4.1 Troubleshooting Guide

Error Messages
Understanding Messages
Chapter 678
• Description: The given directory could not be removed because vxconfigd could not fork
in order to run the rm utility. This is not a serious error. The only side effect of a directory
not being removed is that the directory and its contents will continue to use space in the
root file system. The most likely cause for this error is that your system does not have
enough memory or paging space to allow vxconfigd to fork.
• Action: If your system is this low on memory or paging space, your overall system
performance is probably substantially degraded. Consider adding more memory or paging
space.
V-5-1-116
VxVM vxconfigd WARNING V-5-1-116 Cannot open log file log_filename: reason
• Description: The vxconfigd console output log file could not be opened for the given reason.
• Action: Create any needed directories, or use a different log file path name as described in
“Logging Error Messages” on page 65".
V-5-1-117
VxVM vxconfigd ERROR V-5-1-117 Cannot start volume volume, no valid plexes
• Description: This error indicates that the volume cannot be started because it does not
contain any valid plexes. This can happen, for example, if disk failures have caused all
plexes to be unusable. It can also happen as a result of actions that caused all plexes to
become unusable (for example, forcing the dissociation of subdisks or detaching,
dissociation, or offlining of plexes).
• Action: It is possible that this error results from a drive that failed to spin up. If so,
rebooting may fix the problem. If that does not fix the problem, then the only recourse is to
repair the disks involved with the plexes and restore the file system from a backup.
V-5-1-121
VxVM vxconfigd NOTICE V-5-1-121 Detached disk disk
• Description: The named disk appears to have become unusable and was detached from its
disk group. Additional messages may appear to indicate other records detached as a result
of the disk detach.
• Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the
disk failure are taken care of automatically. Mail is sent to root indicating what actions
were taken by VxVM and what further actions the administrator should take.