VERITAS Volume Manager 5.0 Troubleshooting Guide HP-UX 11i v2 First Edition Manufacturing Part Number: 5991-5854 September 2006 Printed in the United States © Copyright 2006 Hewlett-Packard Development Company L.P.
Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Chapter 1 Recovery from hardware failure Listing unstartable volumes ......................................................................................10 Displaying volume and plex states ...........................................................................10 Understanding the plex state cycle ...........................................................................11 Recovering an unstartable mirrored volume .............................................................
Contents Starting VxVM after booting from recovery media .........................................37 Recovering the root volume after VxVM emergency startup ...........................37 Fixing a missing or corrupt /etc/vx/volboot file ...............................................38 Using VxVM Maintenance Mode Boot ....................................................................38 Recovery by reinstallation ........................................................................................
Preface The VERITAS Volume Manager 5.0 Troubleshooting Guide provides information on the August 2006 release of the VERITAS Volume Manager. Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service.
• http://itrc.hp.com For technical support visit: • http://welcome.hp.com/country/us/en/support.html Typographic Conventions Table 1 describes the typographic conventions used in this document. Table 1 Typographic Conventions Typeface Usage Examples monospace Computer output, files, directories, software elements such as command options, function names, and parameters Read tunables from the /etc/vx/tunefstab file.
• VERITAS 5.0 Installation Guide • VERITAS File System 5.0 Release Notes • VERITAS File System 5.0 Administrator’s Guide • VERITAS Volume Manager 5.0 Release Notes • VERITAS Volume Manager 5.0 Adminstrator’s Guide • VERITAS Volume Manager 5.0 Migration Guide • VERITAS Enterprise Administrator User’s Guide HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs.
Chapter 1 Recovery from hardware failure Symantec’s Veritas Volume Manager (VxVM) protects systems from disk and other hardware failures and helps you to recover from such events. This chapter describes recovery procedures and information to help you prevent loss of data or system access due to disk and other hardware failures. If a volume has a disk I/O failure (for example, because the disk has an uncorrectable error), VxVM can detach the plex involved in the failure.
Recovery from hardware failure Listing unstartable volumes Listing unstartable volumes An unstartable volume can be incorrectly configured or have other errors or conditions that prevent it from being started. To display unstartable volumes, use the vxinfo command. This displays information about the accessibility and usability of volumes: # vxinfo [-g diskgroup] [volume ...
Recovery from hardware failure Understanding the plex state cycle Understanding the plex state cycle Changing plex states are part of normal operations, and do not necessarily indicate abnormalities that must be corrected. A clear understanding of the various plex states and their interrelationship is necessary if you want to be able to perform the recovery procedures described in this chapter. Figure 1-1 shows the main transitions that take place between plex states in VxVM.
Recovery from hardware failure Understanding the plex state cycle Figure 1-2 Additional plex state transitions Create plex PS: EMPTY PKS: DISABLED PS: ACTIVE PKS: DISABLED After crash and reboot (vxvol start) Start up (vxvol start) Initialize plex (vxvol init clean) PS: CLEAN PKS: DISABLED Shut down (vxvol stop) Recover data (vxvol resync) Take plex offline (vxmend off) PS: ACTIVE PKS: ENABLED PS: OFFLINE PKS: DISABLED Resync data (vxplex att) Put plex online (vxmend on) Uncorrectable I/O f
Recovery from hardware failure Recovering an unstartable mirrored volume Recovering an unstartable mirrored volume A system crash or an I/O error can corrupt one or more plexes of a mirrored volume and leave no plex CLEAN or ACTIVE.
Recovery from hardware failure Recovering an unstartable volume with a disabled plex in the RECOVER state Recovering an unstartable volume with a disabled plex in the RECOVER state A plex is shown in the RECOVER state if its contents are out-of-date with respect to the volume. This can happen if a disk containing one or more of the plex’s subdisks has been replaced or reattached.
Recovery from hardware failure Forcibly restarting a disabled volume Forcibly restarting a disabled volume If a disk failure caused a volume to be disabled, and the volume does not contain any valid redundant plexes, you must restore the volume from a backup after replacing the failed disk.
Recovery from hardware failure Reattaching failed disks c1t2d0 c1t3d0 . . . auto:simple auto:simple mydg02 mydg03 mydg mydg online online Reattaching failed disks You can perform a reattach operation if a disk could not be found at system startup, or if VxVM is started with some disk drivers unloaded and unloadable (causing disks to enter the failed state).
Recovery from hardware failure Failures on RAID-5 volumes Failures on RAID-5 volumes Failures are seen in two varieties: system failures and disk failures. A system failure means that the system has abruptly ceased to operate due to an operating system panic or power failure. Disk failures imply that the data on some number of disks has become unavailable due to a system failure (such as a head crash, electronics failure on disk, or disk controller failure).
Recovery from hardware failure Failures on RAID-5 volumes If an attempt is made to read data contained on a stale subdisk, the data is reconstructed from data on all other stripe units in the stripe. This operation is called a reconstructingread. This is a more expensive operation than simply reading the data and can result in degraded read performance. When a RAID-5 volume has stale subdisks, it is considered to be in degraded mode.
Recovery from hardware failure Failures on RAID-5 volumes sd pl sd pl sd disk03-01 r5vol-02 disk04-01 r5vol-03 disk05-01 r5vol-01disk03 r5vol DISABLED r5vol-02disk04 r5vol ENABLED r5vol-12disk05 0 BADLOG 0 LOG 0 102400 1440 1440 1440 1440 2/0 CONCAT 0 CONCAT 0 c2t11d0 c2t12d0 c2t14d0 ENA RW ENA RW ENA Default startup recovery process for RAID-5 VxVM may need to perform several operations to restore fully the contents of a RAID-5 volume and make it usable.
Recovery from hardware failure Failures on RAID-5 volumes ■ Parity resynchronization ■ Log plex recovery ■ Stale subdisk recovery Parity resynchronization and stale subdisk recovery are typically performed when the RAID-5 volume is started, or shortly after the system boots. They can also be performed by running the vxrecover command. For more information on starting RAID-5 volumes, see “Starting RAID-5 volumes” on page 23.
Recovery from hardware failure Failures on RAID-5 volumes v pl sd sd sd ... r5vol r5vol-01 disk01-01 disk02-01 disk03-01 ENABLED r5vol ENABLED r5vol-01disk01 r5vol-01disk02 r5vol-01disk03 NEEDSYNC ACTIVE 0 0 0 204800 204800 102400 102400 102400 RAID RAID 0/0 1/0 2/0 3/16 c2t9d0 c2t10d0 c2t11d0 raid5 RW ENA dS ENA This output lists the volume state as NEEDSYNC, indicating that the parity needs to be resynchronized.
Recovery from hardware failure Failures on RAID-5 volumes Stale subdisk recovery Stale subdisk recovery is usually done at volume start time. However, the process doing the recovery can crash, or the volume may be started with an option such as -o delayrecover that prevents subdisk recovery. In addition, the disk on which the subdisk resides can be replaced without recovery operations being performed. In such cases, you can perform subdisk recovery using the vxvol recover command.
Recovery from hardware failure Failures on RAID-5 volumes Starting RAID-5 volumes When a RAID-5 volume is started, it can be in one of many states. After a normal system shutdown, the volume should be clean and require no recovery. However, if the volume was not closed, or was not unmounted before a crash, it can require recovery when it is started, before it can be made available. This section describes actions that can be taken under certain conditions.
Recovery from hardware failure Failures on RAID-5 volumes Figure 1-3 disk00-00 disk03-00 Invalid RAID-5 volume disk01-00 disk04-00 disk02-00 disk05-00 W Data Data Parity W X Data Parity Data X Y Parity Data Data Y Z Data Data Parity Z RAID-5 plex This example shows four stripes in the RAID-5 array. All parity is stale and subdisk disk05-00 has failed. This makes stripes X and Y unusable because two failures have occurred within those stripes.
Recovery from hardware failure Recovering from incomplete disk group moves # vxmend [-g diskgroup] fix unstale subdisk ■ If some subdisks are stale and need recovery, and if valid logs exist, the volume is enabled by placing it in the ENABLED kernel state and the volume is available for use during the subdisk recovery. Otherwise, the volume kernel state is set to DETACHED and it is not available during subdisk recovery.
Recovery from hardware failure Recovering from incomplete disk group moves This operation fails if one of the disk groups cannot be imported because it has been imported on another host or because it does not exist: VxVM vxdg ERROR V-5-1-2907 diskgroup: Disk group does not exist If the recovery fails, perform one of the following steps as appropriate. ◆ If the disk group has been imported on another host, export it from that host, and import it on the current host.
Recovery from hardware failure Recovery from failure of a DCO volume Recovery from failure of a DCO volume Note: The procedures in this section depend on the DCO version number. See the Veritas Volume Manager Administrator’s Guide for information about DCO versioning. Persistent FastResync uses a data change object (DCO) volume to perform tracking of changed regions in a volume. If an error occurs while reading or writing a DCO volume, it is detached and the badlog flag is set on the DCO.
Recovery from hardware failure Recovery from failure of a DCO volume the entries for the snap objects, vol1_snp and SNAP-vol1_snp, that point to vol1 and SNAP-vol1 respectively.
Recovery from hardware failure Recovery from failure of a DCO volume Recovering a version 0 DCO For a version 0 DCO, perform the following steps to recover the DCO volume: 1 Correct the problem that caused the I/O failure.
Recovery from hardware failure Recovery from failure of a DCO volume 5 To snap back the snapshot volume on which you performed a snapclear in the previous step, use the following command (after using the vxdg move command to move the snapshot plex back to the original disk group, if necessary): # vxplex -f [-g diskgroup] snapback volume snapvol_plex For the example output, the command would take this form: # vxplex -f -g mydg snapback vol1 vol1-03 Note: You cannot use vxassist snapback because the sn
Chapter 2 Recovery from failure of instant snapshot operations This chapter describes how to recover from various failure and error conditions that may occur during instant snapshot operations: ■ Failure of vxsnap prepare ■ Failure of vxsnap make for full-sized instant snapshots ■ Failure of vxsnap make for break-off instant snapshots ■ Failure of vxsnap make for space-optimized instant snapshots ■ Failure of vxsnap restore ■ Failure of vxsnap reattach or refresh ■ Copy-on-write failure ■ I
Recovery from failure of instant snapshot operations Failure of vxsnap make for full-sized instant snapshots Failure of vxsnap make for full-sized instant snapshots If a vxsnap make operation fails during the creation of a full-sized instant snapshot, the snapshot volume may go into the DISABLED state, be marked invalid and be rendered unstartable.
Recovery from failure of instant snapshot operations Failure of vxsnap restore If the vxsnap make operation was being performed on a prepared cache object by specifying the cache attribute, the cache object remains intact after deleting the snapshot. If the cachesize attribute was used to specify a new cache object, the cache object does not exist after deleting the snapshot. Failure of vxsnap restore If a vxsnap restore operation fails, the volume being restored may go into the DISABLED state.
Recovery from failure of instant snapshot operations I/O errors during resynchronization 3 Prepare the volume using the following command: # vxsnap [-g diskgroup] prepare volume [ndcomirs=number] \ [regionsize=size] [drl=yes|no|sequential] \ [storage_attribute ...] See the Veritas Volume Manager Administrator’s Guide and the vxsnap(1M) manual page for full details of how to use the vxsnap prepare command. The volume can now be used again for snapshot operations.
Chapter 3 Recovery from boot disk failure Veritas Volume Manager (VxVM) protects systems from disk and other hardware failures and helps you to recover from such events. This chapter describes recovery procedures and provides information that help to prevent loss of data or system access due to the failure of the boot (root) disk. For information about recovering volumes and their data on non-boot disks, see “Recovery from hardware failure” on page 9.
Recovery from boot disk failure Recovery by booting from recovery media Recovery by booting from recovery media If there is a failure to boot from the VxVM boot disk on HP-UX 11i version 2, and no bootable root mirror is available, it may be necessary to boot from an alternate boot source, or from recovery media such as the following: ■ HP-UX 11i version 2 installation disc. ■ Bootable recovery tape. ■ Secondary boot disk in the configuration.
Recovery from boot disk failure Recovery by booting from recovery media Starting VxVM after booting from recovery media You can use the vx_emerg_start utility to start VxVM after booting a system from recovery media. This command allows a rootable VxVM configuration to be repaired in the event of a catastrophic failure. The command is invoked as shown here: # vx_emerg_start hostname The hostname argument specifies the name (node name) of the system that you are repairing.
Recovery from boot disk failure Using VxVM Maintenance Mode Boot The following form of the vx_emerg_start command combines all these operations in a single command to recover the root volume and its mirrors, check the root file system, and mount it: # vx_emerg_start -m hostname When you have recovered the volumes on the VxVM root disk, and performed any other necessary repairs, reboot the system: # reboot Fixing a missing or corrupt /etc/vx/volboot file The following messages may be displayed at boot
Recovery from boot disk failure Recovery by reinstallation Caution: The VxVM configuration daemon, vxconfigd, does not normally run in MMB mode, and only one copy of the root volume data is used. If the system has a mirrored root volume, writing to the root file system can thus cause file system corruption when both mirrors are subsequently configured. To prevent this, start VxVM in MMB mode by running the vx_emerg_start command.
Recovery from boot disk failure Recovery by reinstallation
Chapter 4 Logging commands and transactions This chapter provides information on how to administer logging of commands and transactions in Veritas Volume Manager 5.0 (VxVM). For information on how to administer error logging, see “Error messages” on page 53. Logging commands The vxcmdlog command allows you to log the invocation of other VxVM commands to a file.
Logging commands and transactions Logging commands If you want to preserve the settings of the vxcmdlog utility, you must also copy the settings file, .cmdlog, to the new directory. Note: The .cmdlog file is a binary and should not be edited. The size of the command log is checked after an entry has been written so the actual size may be slightly larger than that specified.
Logging commands and transactions Logging commands See the vxcmdlog(1M) manual page for more information about the vxcmdlog utility.
Logging commands and transactions Logging transactions Logging transactions The vxtranslog command allows you to log VxVM transactions to a file. The following table demonstrates the usage of vxtranslog: Table 4-2 Examples of vxtranslog usage Command Description vxtranslog -l List current settings for transaction logging. vxtranslog -m on Turn on transaction logging. vxtranslog -s 512k Set the maximum transaction log file size to 512K.
Logging commands and transactions Logging transactions Fri Oct 17 13:23:30 2003 Clid = 23460, PID = 21240, Part = 0, Status = 0, Abort Reason = 0 DA_GET Disk_0 DISK_GET_ATTRS Disk_0 DISK_DISK_OP Disk_0 8 DEVNO_GET Disk_0 DANAME_GET 0x160045 0x160072 GET_ARRAYNAME Disk DISKS CTLR_PTOLNAME 11-08-01 GET_ARRAYNAME Disk DISKS CTLR_PTOLNAME 21-08-01 DROPPED The first line of each log entry is the time stamp of the transaction.
Logging commands and transactions Associating command and transaction logs Associating command and transaction logs The Client and process IDs that are recorded for every request and command assist you in correlating entries in the command and transaction logs.
Chapter 5 Backing up and restoring disk group configurations Disk group configuration backup and restoration allows you to backup and restore all configuration data for Veritas Volume Manager (VxVM) disk groups, and for VxVM objects such as volumes that are configured within the disk groups. Using this feature, you can recover from corruption of a disk group’s configuration that is stored as metadata in the private region of a VM disk.
Backing up and restoring disk group configurations Backing up a disk group configuration Invalid block number Invalid magic number If VxVM cannot update a disk group’s configuration because of disk errors, it disables the disk group and displays the following error: VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors If such errors occur, you can restore the disk group configuration from a backup after you have corrected any underlying problem such as failed or disconnected hardware.
Backing up and restoring disk group configurations Restoring a disk group configuration Caution: Take care that you do not overwrite any files on the target system that are used by a disk group on that system. To back up a disk group manually, use this command: # /etc/vx/bin/vxconfigbackup diskgroup To back up all disk groups, use this version of the command: # /etc/vx/bin/vxconfigbackup For more information, see the vxconfigbackup(1M) manual page.
Backing up and restoring disk group configurations Restoring a disk group configuration To commit the changes that are required to restore the disk group configuration, use the following command: # /etc/vx/bin/vxconfigrestore -c [-l directory] \ {diskgroup | dgid} If no disk headers are reinstalled, the configuration copies in the disks’ private regions are updated from the latest binary copy of the configuration that was saved for the disk group.
Backing up and restoring disk group configurations Restoring a disk group configuration The following is a sample extract from such a backup file that shows the timestamp and disk group ID information: TIMESTAMP Tue Apr 15 23:27:01 PDT 2003 . . . DISK_GROUP_CONFIGURATION Group: mydg dgid: 1047336696.19.xxx.veritas.com . . .
Backing up and restoring disk group configurations Restoring a disk group configuration
Chapter 6 Error messages This chapter provides information on error messages associated with the Veritas Volume Manager 5.0 (VxVM) configuration daemon (vxconfigd), the kernel, and other utilities. It covers most informational, failure, and error messages displayed on the console by vxconfigd, and by the Veritas Volume Manager 5.0 kernel driver, vxio. These include some errors that are infrequently encountered and difficult to troubleshoot.
Error messages Logging error messages If syslog output is enabled, messages with a priority higher than Debug are written to / var/adm/syslog/syslog.log. To enable logging of debug output to the default debug log file, /var/adm/configd.log, edit the startup script for vxconfigd as described in “Configuring logging in the startup script” on page 54, or use the following command: # vxdctl debug level [pathname] There are 10 possible levels of debug logging with the values 0 through 9.
Error messages Understanding messages Note: By default, vxconfigd is started at boot time with the -x syslog option. This redirects vxconfigd console messages to syslog. If you want to retain this behavior when restarting vxconfigd from the command line, include the -x syslog argument, as restarting vxconfigd does not preserve the option settings with which it was previously running. Similarly, any Veritas Volume Manager 5.
Error messages Understanding messages Messages are divided into the following types of severity in decreasing order of impact on the system: PANIC A panic is a severe event as it halts a system during its normal operation. A panic message from the kernel module or from a device driver indicates a hardware problem or software inconsistency so severe that the system cannot continue.
Error messages Understanding messages The unique message number consists of an alpha-numeric string that begins with the letter “V”. For example, in the message number, V-5-1-3141, “V” indicates that this is a Veritas product error message, the first numeric field (5) encodes the product (in this case, VxVM), the second field (1) represents information about the product component, and the third field (3141) is the message index. The text of the error message follows the message number.
Error messages Understanding messages V-5-0-34 VxVM vxdmp NOTICE V-5-0-34 added disk array disk_array_serial_number ■ Description: A new disk array has been added to the host. ■ Action: None. V-5-0-35 VxVM vxdmp NOTICE V-5-0-35 Attempt to disable controller controller_name failed. Rootdisk has just one enabled path. ■ Description: An attempt is being made to disable the one remaining active path to the root disk controller. ■ Action: The path cannot be disabled.
Error messages Understanding messages V-5-0-110 VxVM vxdmp NOTICE V-5-0-110 disabled controller controller_name connected to disk array disk_array_serial_number ■ Description: All paths through the controller connected to the disk array are disabled. This usually happens if a controller is disabled for maintenance. ■ Action: None. V-5-0-111 VxVM vxdmp NOTICE V-5-0-111 disabled dmpnode dmpnode_device_number ■ Description: A DMP node has been marked disabled in the DMP database.
Error messages Understanding messages V-5-0-145 VxVM vxio WARNING V-5-0-145 DRL volume volume is detached ■ Description: 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. ■ Action: The volume containing the DRL log continues in operation.
Error messages Understanding messages V-5-0-164 VxVM vxio WARNING V-5-0-164 Failed to join cluster name, aborting ■ Description: 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. ■ Action: Use the vxdisk -s list command on the master node to see what disks should be visible to the slave node.
Error messages Understanding messages V-5-0-181 VxVM vxio WARNING V-5-0-181 Illegal vminor encountered ■ Description: An attempt was made to open a volume device before vxconfigd loaded the volume configuration. ■ Action: None; under normal startup conditions, this message should not occur. If necessary, start VxVM and re-attempt the operation. V-5-0-194 VxVM vxio WARNING V-5-0-194 Kernel log full: volume detached ■ Description: A plex detach failed because the kernel log was full.
Error messages Understanding messages V-5-0-237 VxVM vxio WARNING V-5-0-237 object subdisk detached from RAID-5 volume at column column offset offset ■ Description: A subdisk was detached from a RAID-5 volume because of the failure of a disk or an uncorrectable error occurring on that disk. ■ Action: Check for other console error messages indicating the cause of the failure. Replace a failed disk as soon as possible.
Error messages Understanding messages V-5-0-251 VxVM vxio WARNING V-5-0-251 read error on object object of mirror plex in volume volume (start offset length length) ■ Description: An error was detected while reading from a mirror. This error may lead to further action shown by later error messages. ■ Action: 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.
Error messages Understanding messages V-5-0-386 VxVM vxio WARNING V-5-0-386 subdisk subdisk failed in plex plex in volume volume ■ Description: The kernel has detected a subdisk failure, which may mean that the underlying disk is failing. ■ Action: 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.
Error messages Understanding messages V-5-1-111 VxVM vxconfigd WARNING V-5-1-111 Cannot fork to remove directory directory: reason ■ 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.
Error messages Understanding messages ■ Action: If hot-relocation is enabled, Veritas Volume Manager 5.0 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. V-5-1-122 VxVM vxconfigd WARNING V-5-1-122 Detaching plex plex from volume volume ■ Description: This error only happens for volumes that are started automatically by vxconfigd at system startup.
Error messages Understanding messages VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors ■ Action: 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. V-5-1-134 VxVM vxconfigd ERROR V-5-1-134 Memory allocation failure ■ Description: This implies that there is insufficient memory to start VxVM.
Error messages Understanding messages ■ ■ The Veritas Volume Manager 5.0 package installation did not complete correctly. ■ The device node was removed by the administrator or by an errant shell script. Action: If the reason is “Device is already open,” stop or kill the old vxconfigd by running the command: # vxdctl -k stop For other failure reasons, consider re-adding the base Veritas Volume Manager 5.0 package. This will reconfigure the device node and re-install the Veritas Volume Manager 5.
Error messages Understanding messages ■ Action: If you want to reset the kernel devices, track down and kill all processes that have a volume or Veritas Volume Manager 5.0 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.
Error messages Understanding messages V-5-1-527 VxVM vxconfigd NOTICE V-5-1-527 Detached subdisk subdisk in volume volume ■ Description: 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. ■ Action: If hot-relocation is enabled, Veritas Volume Manager 5.0 objects affected by the disk failure are taken care of automatically.
Error messages Understanding messages V-5-1-545 VxVM vxconfigd WARNING V-5-1-545 Disk disk in group group locked by host hostid Disk skipped ■ Description: The given disk is listed as locked by the host with the Veritas Volume Manager 5.0 host ID (usually the same as the system host name). ■ Action: 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.
Error messages Understanding messages V-5-1-557 VxVM vxconfigd ERROR V-5-1-557 Disk disk, group group, device device: not updated with new host ID Error: reason ■ Description: This can result from using vxdctl hostid to change the Veritas Volume Manager 5.0 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.
Error messages Understanding messages V-5-1-569 VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk:Cannot autoimport group: reason ■ Description: 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.
Error messages Understanding messages V-5-1-571 VxVM vxconfigd ERROR V-5-1-571 Disk group group, Disk disk: Skip disk group with duplicate name ■ ■ Description: 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.
Error messages Understanding messages V-5-1-579 VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some configuration copies: Disk disk, copy number: [Block number]: reason ... ■ Description: 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.
Error messages Understanding messages 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.
Error messages Understanding messages V-5-1-663 VxVM vxconfigd WARNING V-5-1-663 Group group: Duplicate virtual device number(s): Volume volume remapped from major,minor to major,minor ... ■ Description: 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.
Error messages Understanding messages V-5-1-809 VxVM vxplex ERROR V-5-1-809 Plex plex in volume volume is locked by another utility. ■ Description: 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.
Error messages Understanding messages ■ ■ Case 2: The system somehow has a duplicate boot disk group, one of which contains the /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).
Error messages Understanding messages 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 ■ Description: Regular startup of vxconfigd failed. This error can also result from the command vxdctl enable. vxconfigd is continuing to run, but no configuration updates are possible until the error condition is repaired.
Error messages Understanding messages V-5-1-2198 VxVM vxconfigd ERROR V-5-1-2198 node N: vxconfigd not ready ■ Description: The vxconfigd daemon is not responding properly in a cluster. ■ Action: Stop and restart the vxconfigd daemon on the node indicated.
Error messages Understanding messages utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted. 2 Recreate the temporary database files for all imported disk groups using the following command: # 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.
Error messages Understanding messages V-5-1-2830 VxVM vxconfigd ERROR V-5-1-2830 Disk reserved by other host ■ Description: An attempt was made to online a disk whose controller has been reserved by another host in the cluster. ■ Action: No action is necessary. The cluster manager frees the disk and VxVM puts it online when the node joins the cluster.
Error messages Understanding messages V-5-1-2879 VxVM vxdg ERROR V-5-1-2879 subdisk: Record is associated ■ Description: The named subdisk is not a top-level object. ■ Action: Objects specified for a disk group move, split or join must be either disks or top-level volumes. V-5-1-2907 VxVM vxdg ERROR V-5-1-2907 diskgroup: Disk group does not exist ■ Description: The disk group does not exist or is not imported ■ Action: Use the correct name, or import the disk group and try again.
Error messages Understanding messages V-5-1-2928 VxVM vxdg ERROR V-5-1-2928 diskgroup: Configuration too large for configuration copies ■ Description: The disk group’s configuration database is too small to hold the expanded configuration after a disk group move or join operation. ■ Action: None.
Error messages Understanding messages V-5-1-3020 VxVM vxconfigd ERROR V-5-1-3020 Error in cluster processing ■ Description: 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. ■ Action: Perform the operation from the master node.
Error messages Understanding messages ■ Action: If the system does not appear to be degraded, stop and restart vxconfigd, and try again. V-5-1-3030 VxVM vxconfigd ERROR V-5-1-3030 Volume recovery in progress ■ Description: A node that crashed attempted to rejoin the cluster before its DRL map was merged into the recovery map. ■ Action: Retry the join when the merge operation has completed.
Error messages Understanding messages V-5-1-3034 VxVM vxconfigd ERROR V-5-1-3034 Join not currently allowed ■ Description: A slave attempted to join a cluster when the master was not ready. The slave will retry automatically. ■ Action: No action is necessary if the join eventually completes. Otherwise, investigate the cluster monitor on the master.
Error messages Understanding messages V-5-1-3091 VxVM vxdg ERROR V-5-1-3091 diskname : Disk not moving, but subdisks on it are ■ Description: Some volumes have subdisks that are not on the disks implied by the supplied list of objects. ■ Action: Use the -o expand option to vxdg listmove to produce a self-contained list of objects. V-5-1-3212 VxVM vxconfigd ERROR V-5-1-3212 Insufficient DRL log size: logging is disabled.
Error messages Understanding messages V-5-1-3689 VxVM vxassist ERROR V-5-1-3689 Volume record id rid is not found in the configuration. ■ Description: 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.
Error messages Understanding messages ■ Action: 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 incomplete disk group moves” on page 25 for more information.
Error messages Understanding messages V-5-1-4620 VxVM vxassist WARNING V-5-1-4620 Error while retrieving information from SAL ■ Description: 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. ■ Action: If a connection to SAL is desired, ensure that the correct version of SAL is installed and configured correctly.
Error messages Understanding messages V-5-1-5161 VxVM vxplex ERROR V-5-1-5161 Plex plex not attached. ■ Description: An attempt was made to snap back a detached plex. ■ Action: Reattach the snapshot plex to the snapshot volume. V-5-1-5162 VxVM vxplex ERROR V-5-1-5162 Plexes do not belong to the same snapshot volume. ■ Description: An attempt was made to snap back plexes that belong to different snapshot volumes. ■ Action: Specify the plexes in separate invocations of vxplex snapback.
Error messages Understanding messages ■ Case 2: If disks have been duplicated by using the 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.
Error messages Understanding messages
Index Symbols .cmdlog file 42 .translog file 44 /etc/vx/cbr/bk/diskgroup.dgid dgid .binconfig file 48 dgid .cfgrec file 48 dgid .diskinfo file 48 dgid.dginfo file 48 /etc/vx/log logging directory 41, 44 /stand/rootconf file 38 /var/adm/configd.log file 53 /var/adm/syslog/syslog.
Index E emergency startup 37 EMPTY plex state 11 ENABLED plex kernel state 11 ENABLED volume kernel state 19 ERROR messages 56 error messages A virtual disk device is open 69 All transactions are disabled 67 Already at highest version 91 Attempt to disable controller failed 90 Attempt to enable a controller that is not available 82 can’t import diskgroup 91 Can’t locate disk(s) 92 Cannot assign minor 88 Cannot auto-import group 47, 74 Cannot find disk on slave node 87 Cannot kill existing daemon 81 cann
Index There are two backups that have the same diskgroup name with different diskgroup id 50 Transaction already in progress 84 transactions are disabled 38 Unable to add portal for cluster 87 Unrecognized operating mode 65 update failed 67 upgrade operation failed 91 Version number of kernel does not match vxconfigd 79 Version out of range for at least one node 89 Vol recovery in progress 88 Volboot file not loaded 38 Volume for mount point /usr not found in rootdg disk group 79 Volume is not startable 23
Index Offlining config copy 78 Path failure 63 read error on object 64 removed disk array 64 Rootdisk has just one enabled path 58 Unable to resolve duplicate diskid 94 Volume entering degraded mode 69 P PANIC messages 56 parity regeneration checkpointing 21 resynchronization for RAID-5 20 stale 17 plex kernel states DISABLED 11, 19 ENABLED 11 plex states ACTIVE 11 BADLOG 18 CLEAN 11 EMPTY 11 IOFAIL 12 LOG 18 STALE 13 plexes defined 11 displaying states of 10 in RECOVER state 14 mapping problems 23 re
Index U udid_mismatch flag 94 V V-5-0-106 58 V-5-0-108 58 V-5-0-110 59 V-5-0-111 59 V-5-0-112 59 V-5-0-144 59 V-5-0-145 60 V-5-0-146 60 V-5-0-147 60 V-5-0-148 60 V-5-0-164 61 V-5-0-166 61 V-5-0-168 61 V-5-0-181 62 V-5-0-194 62 V-5-0-196 62 V-5-0-2 57 V-5-0-207 62 V-5-0-216 62 V-5-0-237 63 V-5-0-243 63 V-5-0-244 63 V-5-0-249 63 V-5-0-251 64 V-5-0-252 64 V-5-0-258 64 V-5-0-34 58 V-5-0-35 58 V-5-0-386 65 V-5-0-4 57 V-5-0-55 58 V-5-1-111 66 V-5-1-116 66 V-5-1-117 66 V-5-1-1171 79 V-5-1-1186 79 V-5-1-121 66 V-
Index V-5-1-3689 91 V-5-1-3828 91 V-5-1-3848 91 V-5-1-4220 91 V-5-1-4267 92 V-5-1-4277 92 V-5-1-4551 92 V-5-1-4620 93 V-5-1-4625 93 V-5-1-480 69 V-5-1-484 70 V-5-1-5150 93 V-5-1-5160 93 V-5-1-5161 94 V-5-1-5162 94 V-5-1-525 70 V-5-1-526 70 V-5-1-527 71 V-5-1-528 71 V-5-1-543 71 V-5-1-544 71 V-5-1-545 72 V-5-1-546 72 V-5-1-554 72 V-5-1-557 73 V-5-1-568 73 V-5-1-569 47, 74 V-5-1-571 75 V-5-1-577 75 V-5-1-579 76, 81 V-5-1-583 76 V-5-1-587 76 V-5-1-5929 94 V-5-1-6012 50 V-5-1-663 78 V-5-1-6840 34 V-5-1-737
Index recovery from failure of 33 vxtranslog controlling transaction logging 44 VxVM emergency startup 37 RAID-5 recovery process 19 starting after booting from recovery media 37 using Maintenance Mode Boot (MMB) 38 vxvol recover command 22 vxvol resync command 21 vxvol start command 13 W WARNING messages 56 warning messages Cannot create device 65 Cannot exec /bin/rm to remove directory 65 Cannot exec /usr/bin/rm to remove directory 65 Cannot find device number 58 Cannot fork to remove directory 66 Canno
Index
