|
|
|
|
|
This section contains a list of messages that you may encounter during the operation of Veritas Volume Manager. However, the list is not exhaustive and the second field may contain the name of different command, driver or module from that shown here.
Descriptions are included to elaborate on the situation or problem that generated a particular message. Wherever possible, a recovery procedure is provided to help you to locate and correct the problem.
If you encounter a product error message, record the unique message number preceding the text of the message. When contacting Veritas Technical Support, either by telephone or by visiting the Veritas Technical Support website, be sure to provide the relevant message number. Veritas Technical Support will use this message number to quickly determine if there are TechNotes or other information available for you.
VxVM vxio WARNING V-5-0-2 object_type object_name block offset:Uncorrectable read error ...
VxVM vxio WARNING V-5-0-2 object_type object_name block offset:Uncorrectable write error ...
A read or write operation from or to the specified Veritas Volume Manager object failed. An error is returned to the application.
These errors may represent lost data. Data may need to be restored and failed media may need to be repaired or replaced. Depending on the type of object failing and on the type of recovery suggested for the object type, an appropriate recovery operation may be necessary.
VxVM vxio WARNING V-5-0-4 Plex plex detached from volume volume
An uncorrectable error was detected by the mirroring code and a mirror copy was detached.
To restore redundancy, it may be necessary to add another mirror. The disk on which the failure occurred should be reformatted or replaced.
This message may also appear during a plex detach operation in a cluster. In this case, no action is required.
VxVM vxdmp NOTICE V-5-0-34 added disk array disk_array_serial_number
A new disk array has been added to the host.
No recovery procedure is required.
VxVM vxdmp NOTICE V-5-0-35 Attempt to disable controller controller_name failed. Rootdisk has just one enabled path.
An attempt is being made to disable the one remaining active path to the root disk controller.
VxVM vxio WARNING V-5-0-55 Cannot find device number for boot_path
vxvm vxdmp WARNING V-5-0-55 Cannot find device number for boot_path
The boot path retrieved from the system PROMs cannot be converted to a valid device number.
Check your PROM settings for the correct boot string. If a target driver, such as an ATF, coexists with VxVM, and the target driver claims the boot disk, the message may be ignored if the device path corresponds to the boot disk.
VxVM vxio WARNING V-5-0-64 cannot log commit record for Diskgroup bootdg: error 28
This message usually means that multipathing is misconfigured.
VxVM vxio WARNING V-5-0-106 detaching RAID-5 volume
Either a double-failure condition in the RAID-5 volume has been detected in the kernel or some other fatal error is preventing further use of the array.
If two or more disks have been lost due to a controller or power failure, use the vxrecover utility to recover them once they have been re-attached to the system. Check for other console error messages that may provide additional information about the failure.
VxVM vxio WARNING V-5-0-108 Device major, minor: Received spurious close
A close was received for an object that was not open. This can only happen if the operating system is not correctly tracking opens and closes.
No action is necessary; the system will continue.
VxVM vxdmp NOTICE V-5-0-110 disabled controller controller_name connected to disk array disk_array_serial_number
All paths through the controller connected to the disk array are disabled. This usually happens if a controller is disabled for maintenance.
No recovery procedure is required.
VxVM vxdmp NOTICE V-5-0-111 disabled dmpnode dmpnode_device_number
A DMP node has been marked disabled in the DMP database. It will no longer be accessible for further IO requests. This occurs when all paths controlled by a DMP node are in the disabled state, and therefore inaccessible.
Check hardware or enable the appropriate controllers to enable at least one path under this DMP node.
VxVM vxdmp NOTICE V-5-0-112 disabled path path_device_number belonging to dmpnode dmpnode_device_number
A path has been marked disabled in the DMP database. This path is controlled by the DMP node indicated by the specified device number. This may be due to a hardware failure.
Check the underlying hardware if you want to recover the desired path.
VxVM vxio WARNING V-5-0-144 Double failure condition detected on RAID-5 volume
I/O errors have been received in more than one column of a RAID-5 volume.
The error can be caused by one of the following problems:
Correct the hardware failures if possible. Then recover the volume using the vxrecover command.
VxVM vxio WARNING V-5-0-145 DRL volume volume is detached
A Dirty Region Logging volume became detached because a DRL log entry could not be written. If this is due to a media failure, other errors may have been logged to the console.
The volume containing the DRL log continues in operation. If the system fails before the DRL has been repaired, a full recovery of the volume's contents may be necessary and will be performed automatically when the system is restarted. To recover from this error, use the vxassist addlog command to add a new DRL log to the volume.
VxVM vxdmp NOTICE V-5-0-146 enabled controller controller_name connected to disk array disk_array_serial_number
All paths through the controller connected to the disk array are enabled. This usually happens if a controller is enabled after maintenance.
No recovery procedure is required.
VxVM vxdmp NOTICE V-5-0-147 enabled dmpnode dmpnode_device_number
A DMP node has been marked enabled in the DMP database. This happens when at least one path controlled by the DMP node has been enabled.
No recovery procedure is required.
VxVM vxdmp NOTICE V-5-0-148 enabled path path_device_number belonging to dmpnode dmpnode_device_number
A path has been marked enabled in the DMP database. This path is controlled by the DMP node indicated by the specified device number. This happens if a previously disabled path has been repaired, the user has reconfigured the DMP database using the vxdctl(1M) command, or the DMP database has been reconfigured automatically.
No recovery procedure is required.
VxVM vxio WARNING V-5-0-164 Failed to join cluster name, aborting
A node failed to join a cluster. This may be caused by the node being unable to see all the shared disks. Other error messages may provide more information about the disks that cannot be found.
Use the vxdisk -s list command on the master node to see what disks should be visible to the slave node. Then check that the operating system and VxVM on the failed node can also see these disks. If the operating system cannot see the disks, check the cabling and hardware configuration of the node. If only VxVM cannot see the disks, use the vxdctl enable command to make it scan again for the disks. When the disks are visible to VxVM on the node, retry the join.
VxVM vxio WARNING V-5-0-166 Failed to log the detach of the DRL volume volume
An attempt failed to write a kernel log entry indicating the loss of a DRL volume. The attempted write to the log failed either because the kernel log is full, or because of a write error to the drive. The volume becomes detached.
Messages about log failures are usually fatal, unless the problem is transient. However, the kernel log is sufficiently redundant that such errors are unlikely to occur.
If the problem is not transient (that is, the drive cannot be fixed and brought back online without data loss), recreate the disk group from scratch and restore all of its volumes from backups. Even if the problem is transient, reboot the system after correcting the problem.
If error messages are seen from the disk driver, it is likely that the last copy of the log failed due to a disk error. Replace the failed drive in the disk group. The log re-initializes on the new drive. Finally force the failed volume into an active state and recover the data.
VxVM vxio WARNING V-5-0-168 Failure in RAID-5 logging operation
Indicates that a RAID-5 log has failed.
To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume.
VxVM vxio WARNING V-5-0-181 Illegal vminor encountered
An attempt was made to open a volume device (other than the root volume device) before vxconfigd loaded the volume configuration.
No recovery procedure is required. Under normal startup conditions, this message should not occur. If necessary, start VxVM and re-attempt the operation.
VxVM vxio WARNING V-5-0-194 Kernel log full: volume detached
A plex detach failed because the kernel log was full. As a result, the mirrored volume will become detached.
This condition is unlikely to occur. The only corrective action is to reboot the system.
VxVM vxio WARNING V-5-0-196 Kernel log update failed: volume detached
Detaching a plex failed because the kernel log could not be flushed to disk. As a result, the mirrored volume became detached. This may be caused by all the disks containing a kernel log going bad.
Repair or replace the failed disks so that kernel logging can once again function.
VxVM vxio WARNING V-5-0-207 log object object_name detached from RAID-5 volume
This message indicates that a RAID-5 log has failed.
To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume.
VxVM vxio WARNING V-5-0-216 mod_install returned errno
A call made to the operating system mod_install function to load the vxio driver failed.
Check for additional console messages that may explain why the load failed. Also check the console messages log file for any additional messages that were logged but not displayed on the console.
VxVM vxio WARNING V-5-0-237 object subdisk detached from RAID-5 volume at column column offset offset
A subdisk was detached from a RAID-5 volume because of the failure of a disk or an uncorrectable error occurring on that disk.
Check for other console error messages indicating the cause of the failure. Replace a failed disk as soon as possible.
VxVM vxio WARNING V-5-0-243 Overlapping mirror plex detached from volume volume
An error has occurred on the last complete plex in a mirrored volume. Any sparse mirrors that map the failing region are detached so that they cannot be accessed to satisfy that failed region inconsistently.
The message indicates that some data in the failing region may no longer be stored redundantly.
VxVM vxdmp NOTICE V-5-0-244 Path failure on major/minor
A path under the control of the DMP driver failed. The device major and minor numbers of the failed device is supplied in the message.
No recovery procedure is required.
VxVM vxio WARNING V-5-0-249 RAID-5 volume entering degraded mode operation
An uncorrectable error has forced a subdisk to detach. At this point, not all data disks exist to provide the data upon request. Instead, parity regions are used to regenerate the data for each stripe in the array. Consequently, access takes longer and involves reading from all drives in the stripe.
Check for other console error messages that indicate the cause of the failure. Replace any failed disks as soon as possible.
VxVM vxio WARNING V-5-0-251 read error on object object of mirror plex in volume volume (start offset length length)
An error was detected while reading from a mirror. This error may lead to further action shown by later error messages.
If the volume is mirrored, no further action is necessary since the alternate mirror's contents will be written to the failing mirror; this is often sufficient to correct media failures. If this error occurs often, but never leads to a plex detach, there may be a marginally defective region on the disk at the position indicated. It may eventually be necessary to remove data from this disk and then to reformat the drive.
See the vxevac(1M) manual page.
If the volume is not mirrored, this message indicates that some data could not be read. The file system or other application reading the data may report an additional error, but in either event, data has been lost. The volume can be partially salvaged and moved to another location if desired.
This message may also appear during a plex detach operation in a cluster. In this case, no action is required.
VxVM vxio NOTICE V-5-0-252 read error on object subdisk of mirror plex in volume volume (start offset length length) corrected
A read error occurred, which caused a read of an alternate mirror and a writeback to the failing region. This writeback was successful and the data was corrected on disk.
No recovery procedure is required. The problem was corrected automatically. Note the location of the failure for future reference. If the same region of the subdisk fails again, this may indicate a more insidious failure and the disk should be reformatted at the next reasonable opportunity.
VxVM vxdmp NOTICE V-5-0-258 removed disk array disk_array_serial_number
A disk array has been disconnected from the host, or some hardware failure has resulted in the disk array becoming inaccessible to the host.
Replace disk array hardware if this has failed.
VxVM vxio WARNING V-5-0-281 Root volumes are not supported on your PROM version.
If your system's PROMs are not a recent OpenBoot PROM type, root volumes are unusable.
If you have set up a root volume, undo the configuration by running vxunroot or removing the rootdev line from /etc/system as soon as possible. Contact your hardware vendor for an upgrade to your PROM level.
VxVM vxio WARNING V-5-0-386 subdisk subdisk failed in plex plex in volume volume
The kernel has detected a subdisk failure, which may mean that the underlying disk is failing.
Check for obvious problems with the disk (such as a disconnected cable). If hot-relocation is enabled and the disk is failing, recovery from subdisk failure is handled automatically.
VxVM vxconfigd ERROR V-5-1-90 mode: Unrecognized operating mode
An invalid string was specified as an argument to the -m option. Valid strings are: enable, disable, and boot.
Supply a correct option argument.
VxVM vxconfigd WARNING V-5-1-91 Cannot create device device_path: reason
vxconfigd cannot create a device node either under /dev/vx/dsk or under /dev/vx/rdsk. This should happen only if the root file system has run out of inodes.
Remove some unwanted files from the root file system. Then, regenerate the device node using this command:
VxVM vxconfigd WARNING V-5-1-92 Cannot exec /usr/bin/rm to remove directory: reason
The given directory could not be removed because the /usr/bin/rm utility could not be executed by vxconfigd. This is not a serious error. The only side effect of a directory not being removed is that the directory and its contents continue to use space in the root file system. However, this does imply that the /usr file system is not mounted, or on some systems, that the rm utility is missing or is not in its usual location. This may be a serious problem for the general running of your system.
If the /usr file system is not mounted, you need to determine how to get it mounted. If the rm utility is missing, or is not in the /usr/bin directory, restore it.
VxVM vxconfigd WARNING V-5-1-111 Cannot fork to remove directory directory: reason
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.
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.
VxVM vxconfigd WARNING V-5-1-116 Cannot open log file log_filename: reason
The vxconfigd console output log file could not be opened for the given reason.
Create any needed directories, or use a different log file path name.
See "How error messages are logged" on page 75.
VxVM vxconfigd ERROR V-5-1-117 Cannot start volume volume, no valid plexes
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).
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.
Restoring the root or /usr file system requires that you have a valid backup.
See "Repair of root or /usr file systems on mirrored volumes" on page 47.
VxVM vxconfigd NOTICE V-5-1-121 Detached disk disk
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.
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.
VxVM vxconfigd WARNING V-5-1-122 Detaching plex plex from volume volume
vxconfigd at system startup (that is, the root and /usr file system volumes). The plex is being detached as a result of I/O failure, disk failure during startup or prior to the last system shutdown or crash, or disk removal prior to the last system shutdown or crash.
root or /usr file system retains the same number of active mirrors, remove the given plex and add a new mirror using the vxassist mirror operation. Also consider replacing any bad disks before running this command.
VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors
This message indicates that some error condition has made it impossible for VxVM to continue to manage changes to a disk group. The major reason for this is that too many disks have failed, making it impossible for vxconfigd to continue to update configuration copies. There should be a preceding error message that indicates the specific error that was encountered.
If the disk group that was disabled is the boot disk group, the following additional error is displayed:
VxVM vxconfigd ERROR V-5-1-104 All transactions are disabled
This additional message indicates that vxconfigd has entered the disabled state, which makes it impossible to change the configuration of any disk group, not just the boot disk group.
If the underlying error resulted from a transient failure, such as a disk cabling error, then you may be able to repair the situation by rebooting. Otherwise, the disk group configuration may have to be recreated, and the contents of any volumes restored from a backup.
See "Restoring a disk group configuration" on page 71.
Failure of the boot disk group may require reinstallation of the system if your system uses a root or /usr file system that is defined on a volume.
VxVM vxconfigd ERROR V-5-1-124 Disk group group: update failed: reason
I/O failures have prevented vxconfigd from updating any active copies of the disk group configuration. This usually implies a large number of disk failures. This error will usually be followed by the error:
VxVM vxconfigd ERROR V-5-1-123 Disk group group:
If the underlying error resulted from a transient failure, such as a disk cabling error, then you may be able to repair the situation by rebooting. Otherwise, the disk group may have to be recreated and restored from a backup.
VxVM vxconfigd ERROR V-5-1-134 Memory allocation failure
This implies that there is insufficient memory to start VxVM.
This error should not normally occur, unless your system has very small amounts of memory. Adding swap space will probably not help because this error is most likely to occur early in the boot sequence, before swap areas have been added.
VxVM vxconfigd FATAL ERROR V-5-1-135 Memory allocation failure during startup
This implies that there is insufficient memory to start up VxVM.
This error should not normally occur, unless your system has very small amounts of memory. Adding swap space probably will not help, because this error is most likely to occur early in the boot sequence, before swap areas have been added.
VxVM vxconfigd ERROR V-5-1-148 System startup failed
Either the root or the /usr file system volume could not be started, rendering the system unusable. The error that resulted in this condition should appear prior to this error message.
Look up other error messages appearing on the console and take the actions suggested in the descriptions of those messages.
VxVM vxconfigd ERROR V-5-1-169 cannot open /dev/vx/config: reason
The /dev/vx/config device could not be opened. vxconfigd uses this device to communicate with the Veritas Volume Manager kernel drivers. The most likely reason is "Device is already open." This indicates that some process (most likely vxconfigd) already has /dev/vx/config open. Less likely reasons are "No such file or directory" or "No such device or address."
The following are likely causes:
If the reason is "Device is already open," stop or kill the old vxconfigd by running the command:
For other failure reasons, consider re-adding the base Veritas Volume Manager package. This will reconfigure the device node and re-install the Veritas Volume Manager kernel device drivers. If you cannot re-install the package, contact Veritas Technical Support for more information.
VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/vfstab: reason
vxconfigd could not open the /etc/vfstab file, for the reason given. The /etc/vfstab file is used to determine which volume (if any) to use for the /usr file system.
This error implies that your root file system is currently unusable. You may be able to repair the root file system by mounting it after booting from a network or CD-ROM root file system.
See "Recovering from boot disk failure" on page 37.
VxVM vxconfigd NOTICE V-5-1-249 Volume volume entering degraded mode
Detaching a subdisk in the named RAID-5 volume has caused the volume to enter "degraded" mode. While in degraded mode, performance of the RAID-5 volume is substantially reduced. More importantly, failure of another subdisk may leave the RAID-5 volume unusable. Also, if the RAID-5 volume does not have an active log, then failure of the system may leave the volume unusable.
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 you should take.
VxVM vxconfigd ERROR V-5-1-480 Cannot reset VxVM kernel: reason
The -r reset option was specified to vxconfigd, but the VxVM kernel drivers could not be reset. The most common reason is "A virtual disk device is open." This implies that a VxVM tracing or volume device is open.
If you want to reset the kernel devices, track down and kill all processes that have a volume or Veritas Volume Manager tracing device open. Also, if any volumes are mounted as file systems, unmount those file systems.
Any reason other than "A virtual disk device is open" does not normally occur unless there is a bug in the operating system or in VxVM.
VxVM vxconfigd ERROR V-5-1-484 Cannot start volume volume, no valid complete plexes
These errors indicate that the volume cannot be started because the volume contains no valid complete 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).
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.
VxVM vxconfigd ERROR V-5-1-485 Cannot start volume volume, volume state is invalid
The volume for the root or /usr file system is in an unexpected state (not ACTIVE, CLEAN, SYNC or NEEDSYNC). This should not happen unless the system administrator circumvents the mechanisms used by VxVM to create these volumes.
The only recourse is to bring up VxVM on a CD-ROM or NFS-mounted root file system and to fix the state of the volume.
See "Repair of root or /usr file systems on mirrored volumes" on page 47.
VxVM vxconfigd NOTICE V-5-1-525 Detached log for volume volume
The DRL or RAID-5 log for the named volume was detached as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
If the log is mirrored, hot-relocation tries to relocate the failed log automatically. Use either vxplex dis or vxsd dis to remove the failing logs. Then, use vxassist addlog to add a new log to the volume.
See the vxassist(1M) manual page.
VxVM vxconfigd NOTICE V-5-1-526 Detached plex plex in volume volume
The specified plex was disabled as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
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.
VxVM vxconfigd NOTICE V-5-1-527 Detached subdisk subdisk in volume volume
The specified subdisk was disabled as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message.
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.
VxVM vxconfigd NOTICE V-5-1-528 Detached volume volume
The specified volume was detached as a result of a disk failure, or as a result of the administrator removing a disk with vxdg -k rmdisk. A failing disk is indicated by a "Detached disk" message. Unless the disk error is transient and can be fixed with a reboot, the contents of the volume should be considered lost.
Contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-543 Differing version of vxconfigd installed
A vxconfigd daemon was started after stopping an earlier vxconfigd with a non-matching version number. This can happen, for example, if you upgrade VxVM and then run vxconfigd without first rebooting.
VxVM vxconfigd WARNING V-5-1-544 Disk disk in group group flagged as shared; Disk skipped
The given disk is listed as shared, but the running version of VxVM does not support shared disk groups.
This message can usually be ignored. If you want to use the disk on this system, use vxdiskadd to add the disk. Do not do this if the disk really is shared with other systems.
VxVM vxconfigd WARNING V-5-1-545 Disk disk in group group locked by host hostid Disk skipped
The given disk is listed as locked by the host with the Veritas Volume Manager host ID (usually the same as the system host name).
This message can usually be ignored. If you want to use the disk on this system, use vxdiskadd to add the disk. Do not do this if the disk really is shared with other systems.
VxVM vxconfigd WARNING V-5-1-546 Disk disk in group group: Disk device not found
No physical disk can be found that matches the named disk in the given disk group. This is equivalent to failure of that disk. (Physical disks are located by matching the disk IDs in the disk group configuration records against the disk IDs stored in the Veritas Volume Manager header on the physical disks.) This error message is displayed for any disk IDs in the configuration that are not located in the disk header of any physical disk. This may result from a transient failure such as a poorly-attached cable, or from a disk that fails to spin up fast enough. Alternately, this may happen as a result of a disk being physically removed from the system, or from a disk that has become unusable due to a head crash or electronics failure.
Any RAID-5 plexes, DRL log plexes, RAID-5 subdisks or mirrored plexes containing subdisks on this disk are unusable. Such disk failures (particularly on multiple disks) may cause one or more volumes to become unusable.
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 you should take.
VxVM vxconfigd WARNING V-5-1-554 Disk disk names group group, but group ID differs
As part of a disk group import, a disk was discovered that had a mismatched disk group name and disk group ID. This disk is not imported. This can only happen if two disk groups have the same name but have different disk group ID values. In such a case, one group is imported along with all its disks and the other group is not. This message appears for disks in the un-selected group.
If the disks should be imported into the group, this must be done by adding the disk to the group at a later stage, during which all configuration information for the disk is lost.
VxVM vxconfigd ERROR V-5-1-557 Disk disk, group group, device device:
not updated with new host ID
Error: reason
This can result from using vxdctl hostid to change the Veritas Volume Manager host ID for the system. The error indicates that one of the disks in a disk group could not be updated with the new host ID. This usually indicates that the disk has become inaccessible or has failed in some other way.
Try running the following command to determine whether the disk is still operational:
If the disk is no longer operational, vxdisk should print a message such as:
device: Error: Disk write failure
This will result in the disk being taken out of active use in its disk group, if it has not already been taken out of use. If the disk is still operational, which should not be the case, vxdisk prints:
If the disk is listed as "Okay," try running vxdctl hostid again. If it still results in an error, contact Veritas Technical Support.
VxVM vxconfigd WARNING V-5-1-568 Disk group group is disabled, disks not updated with new host ID
As a result of failures, the named disk group has become disabled. Earlier error messages should indicate the cause. This message indicates that disks in that disk group were not updated with a new Veritas Volume Manager host ID. This warning message should result only from a vxdctl hostid operation.
Typically, unless a disk group was disabled due to transient errors, there is no way to repair a disabled disk group. The disk group may have to be reconstructed from scratch. If the disk group was disabled due to a transient error such as a cabling problem, then a future reboot may not automatically import the named disk group, due to the change in the system's Veritas Volume Manager host ID. In such a case, import the disk group directly using vxdg import with the -C option.
VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk:Cannot auto-import group: reason
On system startup, vxconfigd failed to import the disk group associated with the named disk. A message related to the specific failure is given in reason. Additional error messages may be displayed that give more information on the specific error. In particular, this is often followed by:
VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some
Disk device, copy number: Block bno: error ...
The most common reason for auto-import failures is excessive numbers of disk failures, making it impossible for VxVM to find correct copies of the disk group configuration database and kernel update log. Disk groups usually have enough copies of this configuration information to make such import failures unlikely.
A more serious failure is indicated by errors such as:
Configuration records are inconsistent
Disk group has no valid configuration copies
Duplicate record in configuration
Format error in configuration copy
These errors indicate that all configuration copies have become corrupt (due to disk failures, writing on the disk by an application or the administrator, or bugs in VxVM).
Some correctable errors may be indicated by other error messages that appear in conjunction with the auto-import failure message. Look up those other errors for more information on their cause.
Failure of an auto-import implies that the volumes in that disk group will not be available for use. If there are file systems on those volumes, then the system may yield further errors resulting from inability to access the volume when mounting the file system.
If the error is clearly caused by excessive disk failures, then you may have to recreate the disk group configuration, and restore the contents of any volumes from a backup.
See "Restoring a disk group configuration" on page 71.
There may be other error messages that appear which provide further information. See those other error messages for more information on how to proceed. If those errors do not make it clear how to proceed, contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-571 Disk group group, Disk disk: Skip disk group with duplicate name
Two disk groups with the same name are tagged for auto-importing by the same host. Disk groups are identified both by a simple name and by a long unique identifier (disk group ID) assigned when the disk group is created. Thus, this error indicates that two disks indicate the same disk group name but a different disk group ID.
VxVM does not allow you to create a disk group or import a disk group from another machine, if that would cause a collision with a disk group that is already imported. Therefore, this error is unlikely to occur under normal use.
The error can occur in the following cases:
-h option to cause the disk group to be auto-imported on reboot from another host. If the second host was already auto-importing a disk group with the same name, then reboot of that host will yield this error.
If you want to import both disk groups, then rename the second disk group on import.
VxVM vxconfigd WARNING V-5-1-577 Disk group group: Disk group log may be too small
Log size should be at least number blocks
The log areas for the disk group have become too small for the size of configuration currently in the group. This message only occurs during disk group import; it can only occur if the disk was inaccessible while new database objects were added to the configuration, and the disk was then made accessible and the system restarted. This should not normally happen without first displaying a message about the database area size.
Reinitialize the disks in the group with larger log areas. Note that this requires that you restore data on the disks from backups.
See the vxdisk(1M) manual page.
To reinitialize all of the disks, detach them from the group with which they are associated, reinitialize and re-add them. Then deport and re-import the disk group to effect the changes to the log areas for the group.
VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some configuration copies: Disk disk, copy number: [Block number]: reason ...
During a failed disk group import, some of the configuration copies in the named disk group were found to have format or other types of errors which make those copies unusable. This message lists all configuration copies that have uncorrected errors, including any appropriate logical block number. If no other reasons are displayed, then this may be the cause of the disk group import failure.
If some of the copies failed due to transient errors (such as cable failures), then a reboot or re-import may succeed in importing the disk group. Otherwise, the disk group configuration may have to be restored.
See "Restoring a disk group configuration" on page 71.
VxVM vxconfigd ERROR V-5-1-583 Disk group group: Reimport of disk group failed: reason
After vxconfigd was stopped and restarted (or disabled and then enabled), VxVM failed to recreate the import of the indicated disk group. The reason for failure is specified. Additional error messages may be displayed that give further information describing the problem.
A major cause for this kind of failure is disk failures that were not addressed before vxconfigd was stopped or disabled. If the problem is a transient disk failure, then rebooting may take care of the condition. The error may be accompanied by messages such as ''Disk group has no valid configuration copies.'' This indicates that the disk group configuration copies have become corrupt (due to disk failures, writing on the disk by an application or the administrator, or bugs in VxVM).
See "Restoring a disk group configuration" on page 71.
VxVM vxdg ERROR V-5-1-587 disk group groupname: import failed: reason
The import of a disk group failed for the specified reason.
The action to be taken depends on the reason given in the error message:
Disk is in use by another host
No valid disk found containing disk group
The first message indicates that disks have been moved from a system that has crashed or that failed to detect the group before the disk was moved. The locks stored on the disks must be cleared.
The second message indicates that the disk group does not contain any valid disks (not that it does not contain any disks). The disks may be considered invalid due to a mismatch between the host ID in their configuration copies and that stored in the /etc/vx/volboot file.
To clear locks on a specific set of devices, use the following command:
# vxdisk clearimport devicename ...
To clear the locks during import, use the following command:
vxdisk clearimport or vxdg -C import command on systems that have dual-ported disks. Clearing the locks allows those disks to be accessed at the same time from multiple hosts and can result in corrupted data.
An import operation fails if some disks for the disk group cannot be found among the disk drives attached to the system.
Disk group has no valid configuration copies
The first message indicates a recoverable error.
The second message indicates a fatal error that requires hardware repair or the creation of a new disk group, and recovery of the disk group configuration and data:
If some of the disks in the disk group have failed, you can force the disk group to be imported with this command:
-f option. It can cause the same disk group to be imported twice from different sets of disks. This can cause the disk group configuration to become inconsistent.
As using the -f option to force the import of an incomplete disk group counts as a successful import, an incomplete disk group may be imported subsequently without this option being specified. This may not be what you expect.
These operations can also be performed using the vxdiskadm utility. To deport a disk group using vxdiskadm, select menu item 9 (Remove access to (deport) a disk group). To import a disk group, select item 8 (Enable access to (import) a disk group). The vxdiskadm import operation checks for host import locks and prompts to see if you want to clear any that are found. It also starts volumes in the disk group.
VxVM vxconfigd WARNING V-5-1-663 Group group: Duplicate virtual device number(s):
Volume volume remapped from major,minor to major,minor ...
The configuration of the named disk group includes conflicting device numbers. A disk group configuration lists the recommended device number to use for each volume in the disk group. If two volumes in two disk groups happen to list the same device number, then one of the volumes must use an alternate device number. This is called device number remapping. Remapping is a temporary change to a volume. If the other disk group is deported and the system is rebooted, then the volume that was remapped may no longer be remapped. Also, volumes that are remapped once are not guaranteed to be remapped to the same device number in further reboots.
Use the vxdg reminor command to renumber all volumes in the offending disk group permanently.
VxVM vxconfigd ERROR V-5-1-737 Mount point path: volume not in bootdg disk group
The volume device listed in the /etc/vfstab file for the given mount-point directory (normally /usr) is listed as in a disk group other than the boot disk group. This error should not occur if the standard Veritas Volume Manager procedures are used for encapsulating the disk containing the /usr file system.
Boot VxVM from a network or CD-ROM mounted root file system. Then, start up VxVM using fixmountroot on a valid mirror disk of the root file system. After starting VxVM, mount the root file system volume and edit the /etc/vfstab file. Change the file to use a direct partition for the file system. There should be a comment in the /etc/vfstab file that indicates which partition to use.
VxVM vxconfigd NOTICE V-5-1-768 Offlining config copy number on disk disk: Reason: reason
An I/O error caused the indicated configuration copy to be disabled. This is a notice only, and does not normally imply serious problems, unless this is the last active configuration copy in the disk group.
Consider replacing the indicated disk, since this error implies that the disk has deteriorated to the point where write errors cannot be repaired automatically. The error can also result from transient problems with cabling or power.
VxVM vxplex ERROR V-5-1-809 Plex plex in volume volume is locked by another utility.
The vxplex command fails because a previous operation to attach a plex did not complete. The vxprint command should show that one or both of the temporary and persistent utility fields (TUTIL0 and PUTIL0) of the volume and one of its plexes are set.
If the vxtask list command does not show a task running for the volume, use the vxmend command to clear the TUTIL0 and PUTIL0 fields for the volume and all its components for which these fields are set:
# vxmend -g diskgroup clear all volume plex ...
VxVM vxplex ERROR V-5-1-923 Record volume is in disk group diskgroup1 plex is in group diskgroup2.
An attempt was made to snap back a plex from a different disk group.
Move the snapshot volume into the same disk group as the original volume.
VxVM vxconfigd FATAL ERROR V-5-1-946 bootdg cannot be imported during boot
This message usually means that multipathing is misconfigured.
VxVM vxconfigd ERROR V-5-1-1049 System boot disk does not have a valid rootvol plex
Please boot from one of the following disks:
DISK MEDIA DEVICE BOOT COMMANDdiskname device boot vx-diskname...
The system is configured to use a volume for the root file system, but was not booted on a disk containing a valid mirror of the root volume. Disks containing valid root mirrors are listed as part of the error message. A disk is usable as a boot disk if there is a root mirror on that disk which is not stale or offline.
Try to boot from one of the named disks using the associated boot command that is listed in the message.
VxVM vxconfigd ERROR V-5-1-1063 There is no volume configured for the root device
The system is configured to boot from a root file system defined on a volume, but there is no root volume listed in the configuration of the boot disk group.
The following are possible causes of this error:
root device is /pseudo/vxio@0:0. This can happen only as a result of direct manipulation by the administrator.
Boot the system on a CD-ROM or networking-mounted root file system, directly mount the disk partition of the root file system, and remove the following lines from /etc/system:
root file system volume and one of which does not, and vxconfigd somehow chose the wrong one. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (reversing the apparent access order of the two disk groups). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.
Either boot the system with all drives in the offending version of the boot disk group turned off, or import and rename the offending boot disk group from another host.
If you turn off the drives, run the following command after booting:
This updates time stamps on the imported version of the specified boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-1171 Version number of kernel does not match vxconfigd
The release of vxconfigd does not match the release of the Veritas Volume Manager kernel drivers. This should happen only as a result of upgrading VxVM, and then running vxconfigd without a reboot.
Reboot the system. If that does not cure the problem, re-add the VxVM packages.
VxVM vxconfigd ERROR V-5-1-1186 Volume volume for mount point /usr not found in bootdg disk group
The system is configured to boot with /usr mounted on a volume, but the volume associated with /usr is not listed in the configuration of the boot disk group.
The following are possible causes of this error:
/etc/vfstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume named is not in the boot disk group. This should happen only as a result of direct manipulation by the administrator.
Boot the system on a CD-ROM or networking-mounted root file system. If the root file system is defined on a volume, then start and mount the root volume. If the root file system is not defined on a volume, mount the root file system directly. Edit the /etc/vfstab file to correct the entry for the /usr file system.
/usr file system volume and one of which does not (or uses a different volume name), and vxconfigd somehow chose the wrong boot disk group. Since vxconfigd chooses the more recently accessed version of the boot disk group, this error can happen if the system clock was updated incorrectly at some point (causing the apparent access order of the two disk groups to be reversed). This can also happen if some disk group was deported and assigned the same name as the boot disk group with locks given to this host.
In case 2, either boot with all drives in the offending version of the boot disk group turned off, or import and rename the offending boot disk group from another host.
If you turn off drives, run the following command after booting:
This updates time stamps on the imported version of the boot disk group, bootdg, which should make the correct version appear to be the more recently accessed. If this does not correct the problem, contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: aborting
Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.
The failure was fatal and vxconfigd was forced to exit. The most likely cause is that the operating system is unable to create interprocess communication channels to other utilities.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Error check group configuration copies. Database file not found
Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.
The directory /var/vxvm/tempdb is inaccessible. This may be because of root file system corruption, a full root file system, or if /var is a separate file system, because it has become corrupted or has not been mounted.
If the root file system is full, increase its size or remove files to make space for the tempdb file.
If /var is a separate file system, make sure that it has an entry in /etc/vfstab. Otherwise, look for I/O error messages during the boot process that indicate either a hardware problem or misconfiguration of any logical volume management software being used for the /var file system. Also verify that the encapsulation (if configured) of your boot disk is complete and correct.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: transactions are disabled
Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable.
vxconfigd continues to run, but no configuration updates are possible until the error condition is repaired.
Additionally, this may be followed with this message:
VxVM vxconfigd ERROR V-5-1-579 Disk group group:
Errors in some configuration copies:
Disk device, copy number: Block bno: error ...
Other error messages may be displayed that further indicate the underlying problem.
Evaluate the error messages to determine the root cause of the problem. Make changes suggested by the errors and then try rerunning the command.
If the "Errors in some configuration copies" error occurs again, that may indicate the real problem lies with the configuration copies in the disk group.
See "Restoring a disk group configuration" on page 71.
VxVM vxconfigd ERROR V-5-1-2020 Cannot kill existing daemon, pid=process_ID
The -k (kill existing vxconfigd process) option was specified, but a running configuration daemon process could not be killed. A configuration daemon process, for purposes of this discussion, is any process that opens the /dev/vx/config device (only one process can open that device at a time). If there is a configuration daemon process already running, then the -k option causes a SIGKILL signal to be sent to that process. If, within a certain period of time, there is still a running configuration daemon process, the error message is displayed.
This error can result from a kernel error that has made the configuration daemon process unkillable, from some other kind of kernel error, or from some other user starting another configuration daemon process after the SIGKILL signal. This last condition can be tested for by running vxconfigd -k again. If the error message reappears, contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-2197 node N: missing vxconfigd
The vxconfigd daemon is not running on the indicated cluster node.
VxVM vxconfigd ERROR V-5-1-2198 node N: vxconfigd not ready
The vxconfigd daemon is not responding properly in a cluster.
Stop and restart the vxconfigd daemon on the node indicated.
VxVM vxconfigd ERROR V-5-1-2274 volume:vxconfigd cannot boot-start RAID-5 volumes
A volume that vxconfigd should start immediately upon booting the system (that is, the volume for the /usr file system) has a RAID-5 layout. The /usr file system should never be defined on a RAID-5 volume.
It is likely that the only recovery for this is to boot VxVM from a network-mounted root file system (or from a CD-ROM), and reconfigure the /usr file system to be defined on a regular non-RAID-5 volume.
VxVM vxdmpadm ERROR V-5-1-2290 Attempt to enable a controller that is not available
This message is returned by the vxdmpadm utility when an attempt is made to enable a controller that is not working or is not physically present.
Check hardware and see if the controller is present and whether I/O can be performed through it.
VxVM vxconfigd ERROR V-5-1-2353 Disk group group: Cannot recover temp database: reason
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
This error can happen if you kill and restart vxconfigd, or if you disable and enable vxconfigd with vxdctl disable and vxdctl enable. The error indicates a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.
If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.
To correct the error without rebooting
vxvol, vxplex, or vxsd processes are running.
Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.
# vxconfigd -x cleartempdir 2> /dev/console
The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.
VxVM vxconfigd ERROR V-5-1:2524 VOL_IO_DAEMON_SET failed: daemon count must be above N while cluster
The number of Veritas Volume Manager kernel daemons (vxiod) is less than the minimum number needed to join a cluster.
Increase the number of daemons using vxiod.
VxVM vxconfigd WARNING V-5-1-2630 library and vxconfigd disagree on existence of client number
This warning may safely be ignored.
No recovery procedure is required.
VxVM vxconfigd ERROR V-5-1-2824 Configuration daemon error 242
A node failed to join a cluster, or a cluster join is taking too long. If the join fails, the node retries the join automatically.
No action is necessary if the join is slow or a retry eventually succeeds.
VxVM vxdg ERROR V-5-1-2829 diskgroup: Disk group version doesn't support feature; see the vxdg upgrade command
The version of the specified disk group does not support disk group move, split or join operations.
Use the vxdg upgrade diskgroup command to update the disk group version.
VxVM vxconfigd ERROR V-5-1-2830 Disk reserved by other host
An attempt was made to online a disk whose controller has been reserved by another host in the cluster.
No action is necessary. The cluster manager frees the disk and VxVM puts it online when the node joins the cluster.
VxVM vxconfigd ERROR V-5-1-2841 enable failed: Error in disk group configuration copies
Unexpected kernel error in configuration update; transactions are disabled.
Usually means that multipathing is misconfigured.
VxVM vxdg ERROR V-5-1-2860 Transaction already in progress
One of the disk groups specified in a disk group move, split or join operation is currently involved in another unrelated disk group move, split or join operation (possibly as the result of recovery from a system failure).
Use the vxprint command to display the status of the disk groups involved. If vxprint shows that the TUTIL0 field for a disk group is set to MOVE, and you are certain that no disk group move, split or join should be in progress, use the vxdg command to clear the field.
See "Recovering from an incomplete disk group move" on page 24.
Otherwise, retry the operation.
VxVM vxdg ERROR V-5-1-2862 object: Operation is not supported
DCO and snap objects dissociated by Persistent FastResync, and VVR objects cannot be moved between disk groups.
No action is necessary. The operation is not supported.
VxVM vxdg ERROR V-5-1-2866 object: Record already exists in disk group
A disk group join operation failed because the name of an object in one disk group is the same as the name of an object in the other disk group. Such name clashes are most likely to occur for snap objects and snapshot plexes.
Use the following command to change the object name in either one of the disk groups:
# vxedit -g diskgroup rename old_name new_name
See the vxedit(1M) manual page.
VxVM vxdg ERROR V-5-1-2870 volume: Volume or plex device is open or mounted
An attempt was made to perform a disk group move, split or join on a disk group containing an open volume.
It is most likely that a file system configured on the volume is still mounted. Stop applications that access volumes configured in the disk group, and unmount any file systems configured in the volumes.
VxVM vxdg ERROR V-5-1-2879 subdisk: Record is associated
The named subdisk is not a top-level object.
Objects specified for a disk group move, split or join must be either disks or top-level volumes.
VxVM vxdg ERROR V-5-1-2907 diskgroup: Disk group does not exist
The disk group does not exist or is not imported
Use the correct name, or import the disk group and try again.
VxVM vxdg ERROR V-5-1-2908 diskdevice: Request crosses disk group boundary
The specified disk device is not configured in the source disk group for a disk group move or split operation.
Correct the name of the disk object specified in the disk group move or split operation.
VxVM vxdg ERROR V-5-1-2911 diskname: Disk is not usable
The specified disk has become unusable.
Do not include the disk in any disk group move, split or join operation until it has been replaced or repaired.
VxVM vxconfigd ERROR V-5-1-2922 Disk group exists and is imported
A slave tried to join a cluster, but a shared disk group already exists in the cluster with the same name as one of its private disk groups.
Use the vxdg -n newname import diskgroup operation to rename either the shared disk group on the master, or the private disk group on the slave.
VxVM vxdg ERROR V-5-1-2928 diskgroup: Configuration too large for configuration copies
The disk group's configuration database is too small to hold the expanded configuration after a disk group move or join operation.
VxVM vxdg ERROR V-5-1-2933 diskgroup: Cannot remove last disk group configuration copy
The requested disk group move, split or join operation would leave the disk group without any configuration copies.
No action is required. The operation is not supported.
VxVM vxassist ERROR V-5-1-2935 No more space in disk group configuration.
There is no more space in the disk group's configuration database for VxVM object records.
Copy the contents of several volumes to another disk group and then delete the volumes from this disk group, or use the disk group split/join feature to move the volumes to another disk group. To avoid the problem in the future, do not create more than a few hundred volumes in a disk group, or specify a larger size for the private region when adding disks to a new disk group.
VxVM vxdg ERROR V-5-1-3009 object: Name conflicts with imported diskgroup
The target disk group of a split operation already exists as an imported disk group.
Choose a different name for the target disk group.
VxVM vxconfigd ERROR V-5-1-3020 Error in cluster processing
This may be due to an operation inconsistent with the current state of a cluster (such as an attempt to import or deport a shared disk group to or from the slave). It may also be caused by an unexpected sequence of commands from vxclust.
Perform the operation from the master node.
VxVM vxconfigd ERROR V-5-1-3022 Cannot find disk on slave node
A slave node in a cluster cannot find a shared disk. This is accompanied by the syslog message:
VxVM vxconfigd ERROR V-5-1-2173 cannot find disk disk
Make sure that the same set of shared disks is online on both nodes. Examine the disks on both the master and the slave with the command vxdisk list and make sure that the same set of disks with the shared flag is visible on both nodes. If not, check the connections to the disks.
VxVM vxconfigd ERROR V-5-1-3023 Disk in use by another cluster
An attempt was made to import a disk group whose disks are stamped with the ID of another cluster.
If the disk group is not imported by another cluster, retry the import using the -C (clear import) flag.
VxVM vxconfigd ERROR V-5-1-3024 vxclust not there
An error during an attempt to join a cluster caused vxclust to fail. This may be caused by the failure of another node during a join or by the failure of vxclust.
Retry the join. An error message on the other node may clarify the problem.
VxVM vxconfigd ERROR V-5-1-3025 Unable to add portal for cluster
vxconfigd was not able to create a portal for communication with the vxconfigd on the other node. This may happen in a degraded system that is experiencing shortages of system resources such as memory or file descriptors.
If the system does not appear to be degraded, stop and restart vxconfigd, and try again.
VxVM vxconfigd ERROR V-5-1-3030 Volume recovery in progress
A node that crashed attempted to rejoin the cluster before its DRL map was merged into the recovery map.
Retry the join when the merge operation has completed.
VxVM vxconfigd ERROR V-5-1-3031 Cannot assign minor minor
A slave attempted to join a cluster, but an existing volume on the slave has the same minor number as a shared volume on the master.
This message is accompanied by the following console message:
VxVM vxconfigd ERROR V-5-1-2192 minor number minor disk group group in use
Before retrying the join, use vxdg reminor (see the vxdg(1M) manual page) to choose a new minor number range either for the disk group on the master or for the conflicting disk group on the slave. If there are open volumes in the disk group, the reminor operation will not take effect until the disk group is deported and updated (either explicitly or by rebooting the system).
VxVM vxconfigd ERROR V-5-1-3032 Master sent no data
During the slave join protocol, a message without data was received from the master. This message is only likely to be seen in the case of an internal VxVM error.
Contact Veritas Technical Support.
VxVM vxconfigd ERROR V-5-1-3033 Join in progress
An attempt was made to import or deport a shared disk group during a cluster reconfiguration.
Retry when the cluster reconfiguration has completed.
VxVM vxconfigd ERROR V-5-1-3034 Join not currently allowed
A slave attempted to join a cluster when the master was not ready. The slave will retry automatically.
No action is necessary if the join eventually completes. Otherwise, investigate the cluster monitor on the master.
VxVM vxconfigd ERROR V-5-1-3042 Clustering license restricts operation
An operation requiring a full clustering license was attempted, and such a license is not available.
If the error occurs when a disk group is being activated, dissociate all but one plex from mirrored volumes before activating the disk group. If the error occurs during a transaction, deactivate the disk group on all nodes except the master.
VxVM vxconfigd ERROR V-5-1-3046 Node activation conflict
The disk group could not be activated because it is activated in a conflicting mode on another node in a cluster.
Retry later, or deactivate the disk group on conflicting nodes.
VxVM vxconfigd ERROR V-5-1-3049 Retry rolling upgrade
An attempt was made to upgrade a cluster to a higher protocol version when a transaction was in progress.
Retry the upgrade at a later time.
VxVM vxconfigd ERROR V-5-1-3050 Version out of range for at least one node
Before trying to upgrade a cluster by running vxdctl upgrade, all nodes should be able to support the new protocol version. An upgrade can fail if at least one of them does not support the new protocol version.
Make sure that the Veritas Volume Manager package that supports the new protocol version is installed on all nodes and retry the upgrade.
VxVM vxdg ERROR V-5-1-3091 diskname : Disk not moving, but subdisks on it are
Some volumes have subdisks that are not on the disks implied by the supplied list of objects.
Use the -o expand option to vxdg listmove to produce a self-contained list of objects.
VxVM vxconfigd ERROR V-5-1-3212 Insufficient DRL log size: logging is disabled.
A volume with an insufficient DRL log size was started successfully, but DRL logging is disabled and a full recovery is performed.
Create a new DRL of sufficient size.
VxVM vxdmpadm ERROR V-5-1-3243 The VxVM restore daemon is already running. You can stop and restart the restore daemon with desired arguments for changing any of its parameters.
The vxdmpadm start restore command has been executed while the restore daemon is already running.
Stop the restore daemon and restart it with the required set of parameters.
See the vxdmpadm(1M) manual page.
VxVM vxdmpadm ERROR V-5-1-3362 Attempt to disable controller failed. One (or more) devices can be accessed only through this controller. Use the -f option if you still want to disable this controller.
Disabling the controller could lead to some devices becoming inaccessible.
To disable the only path connected to a disk, use the -f option.
VxVM vxconfigd ERROR V-5-1-3486 Not in cluster
Checking for the current protocol version (using vxdctl protocol version) does not work if the node is not in a cluster.
Bring the node into the cluster and retry.
VxVM vxassist ERROR V-5-1-3689 Volume record id rid is not found in the configuration.
An error was detected while reattaching a snapshot volume using snapback. This happens if a volume's record identifier (rid) changes as a result of a disk group split that moved the original volume to a new disk group. The snapshot volume is unable to recognize the original volume because its record identifier has changed.
Use the following command to perform the snapback:
# vxplex [-g diskgroup] -f snapback volume plex
VxVM vxconfigd ERROR V-5-1-3828 upgrade operation failed: Already at highest version
An upgrade operation has failed because a cluster is already running at the highest protocol version supported by the master.
No further action is possible as the master is already running at the highest protocol version it can support.
VxVM vxconfigd ERROR V-5-1-3848 Incorrect protocol version (number) in volboot file
A node attempted to join a cluster where VxVM software was incorrectly upgraded or the volboot file is corrupted, possibly by being edited manually. The volboot file should contain a supported protocol version before trying to bring the node into the cluster.
Verify the supported cluster protocol versions using the vxdctl protocolversion command. The volboot file should contain a supported protocol version before trying to bring the node into the cluster. Run vxdctl init to write a valid protocol version to the volboot file. Restart vxconfigd and retry the join.
VxVM vxconfigd ERROR V-5-1-4220 DG move: can't import diskgroup, giving up
The specified disk group cannot be imported during a disk group move operation. (The disk group ID is obtained from the disk group that could be imported.)
The disk group may have been moved to another host. One option is to locate it and use the vxdg recover command on both the source and target disk groups. Specify the -o clean option with one disk group, and the -o remove option with the other disk group.
See "Recovering from an incomplete disk group move" on page 24.
VxVM vxassist WARNING V-5-1-4267 volume volume already has at least one snapshot plex
Snapshot volume created with these plexes will have a dco volume with no associated dco plex.
An error was detected while adding a DCO object and DCO volume to a mirrored volume. There is at least one snapshot plex already created on the volume. Because this snapshot plex was created when no DCO was associated with the volume, there is no DCO plex allocated for it.
See the Veritas Volume Manager Administrator's Guide.
VxVM vxconfigd ERROR V-5-1-4277 cluster_establish: CVM protocol version out of range
When a node joins a cluster, it tries to join at the protocol version that is stored in its volboot file. If the cluster is running at a different protocol version, the master rejects the join and sends the current protocol version to the slave. The slave re-tries with the current version (if that version is supported on the joining node), or the join fails.
Make sure that the joining node has a Veritas Volume Manager release installed that supports the current protocol version of the cluster.
VxVM vxconfigd ERROR V-5-1-4551 dg_move_recover: can't locate disk(s), giving up
Disks involved in a disk group move operation cannot be found, and one of the specified disk groups cannot be imported.
Manual use of the vxdg recover command may be required to clean the disk group to be imported.
See "Recovering from an incomplete disk group move" on page 24.
VxVM vxassist WARNING V-5-1-4620 Error while retrieving information from SAL
The vxassist command does not recognize the version of the SAN Access Layer (SAL) that is being used, or detects an error in the output from SAL.
If a connection to SAL is desired, ensure that the correct version of SAL is installed and configured correctly. Otherwise, suppress communication between vxassist and SAL by adding the following line to the vxassist defaults file (usually /etc/default/vxassist):
VxVM vxassist WARNING V-5-1-4625 SAL authentication failed...
The SAN Access Layer (SAL) rejects the credentials that are supplied by the vxassist command.
If connection to SAL is desired, use the vxspcshow command to set a valid user name and password. Otherwise, suppress communication between vxassist and SAL by adding the following line to the vxassist defaults file (usually /etc/default/vxassist):
VxVM vxassist ERROR V-5-1-5150 Insufficient number of active snapshot mirrors in snapshot_volume.
An attempt to snap back a specified number of snapshot mirrors to their original volume failed.
Specify a number of snapshot mirrors less than or equal to the number in the snapshot volume.
VxVM vxplex ERROR V-5-1-5160 Plex plex not associated to a snapshot volume.
An attempt was made to snap back a plex that is not from a snapshot volume.
Specify a plex from a snapshot volume.
VxVM vxplex ERROR V-5-1-5161 Plex plex not attached.
An attempt was made to snap back a detached plex.
Reattach the snapshot plex to the snapshot volume.
VxVM vxplex ERROR V-5-1-5162 Plexes do not belong to the same snapshot volume.
An attempt was made to snap back plexes that belong to different snapshot volumes.
Specify the plexes in separate invocations of vxplex snapback.
VxVM vxconfigd NOTICE V-5-1-5929 Unable to resolve duplicate diskid.
VxVM has detected disks with duplicate disk identifiers. Arrays with mirroring capability in hardware are particularly susceptible to such data corruption, but other causes are possible as explained below.
In releases prior to 3.5, VxVM selected the first disk that it found if the selection process failed. From release 3.5, the default behavior of VxVM was to avoid the selection of the wrong disk as this could lead to data corruption. If VxVM could not determine which disk was the original, it would not import the disks until they were reinitialized with a new disk ID.
From release 5.0, VxVM checks the unique disk identifier (UDID) value that is known to the Device Discovery Layer (DDL) against the UDID value that is set in the disk's private region. The udid_mismatch flag is set on the disk if the values differ. If set, this flag is displayed in the output from the vxdisk list command.
A new set of vxdisk and vxdg operations are provided to handle such disks; either by either writing the DDL value of the UDID to a disk's private region, or by tagging a disk and specifying that it is a cloned disk to the vxdg import operation.
User intervention is required in the following cases:
dd command or any similar copying utility, you can use the following command to update the UDID for one or more disks:
# vxdisk [-f] updateudid disk ...
This command uses the current value of the UDID that is stored in the Device Discovery Layer (DDL) database to correct the value in the private region. The -f option must be specified if VxVM has not set the udid_mismatch flag on a disk.
For example, the following command updates the UDIDs for the disks c2t66d0s2 and c2t67d0s2:
# vxdisk updateudid c2t66d0s2 c2t67d0s2
If DMP is suppressed, VxVM does not know which path to select as the true path. You must choose which path to use. Decide which path to exclude, and then select item 1 (suppress all paths through a controller from VxVM's view) or item 2 (suppress a path from VxVM's view) from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).
suppress all paths through a controller from VxVM's view) from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view). If all bootdg disks are from that array, vxconfigd does not start. (You may also see errors V-5-0-64, V-5-1-946 and V-5-1-2841.)
If only one array is connected to the controller, suppress the path from DMP using item 5 (Prevent multipathing of all disks on a controller by VxVM), and then item 1 (Suppress all paths through a controller from VxVM's view), from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).
If more than one array is connected to the controller, suppress the path from DMP using item 5 (Prevent multipathing of all disks on a controller by VxVM), and then item 2 (Suppress a path from VxVM's view), from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM's view).
VxVM vxdisksetup NOTICE V-5-2-2400 daname: Duplicate DA records encountered for this device.
This may occur if a disk has been replaced in a Sun StorEdgeTM A5x00 (or similar) array without using the luxadm command to notify the operating system. Duplicated disk access record entries similar to the following appear in the output from the vxdisk list command:
c1t5d0s2 sliced c1t5d0s2 - error
c1t5d0s2 sliced c1t5d0s2 - online|error
The status of the second entry may be online or error.
Run the vxdisk list command to ensure that you have removed all entries for the disk access name.
luxadm command to obtain the A5K array name and slot number of the disk, and then use these with luxadm to remove the disk:
luxadm.
This completes the removal of device entries corresponding to the physical disk.
vxdisk list and vxdisk rm commands to list any remaining entries for the disk access name and remove these from VxVM control.
luxadm command to take the disk offline on all the paths to it. The following example shows how to take a disk offline that is connected to controllers c1 and c2:
vxdisk list. This completes the removal of stale device entries for the disk from VxVM.