Veritas Volume Manager 5.
Legal Notices © Copyright 2008 Hewlett-Packard Development Company, L.P. Publication Date: 2008 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 ................................................................................. 8 Displaying volume and plex states ...................................................................... 8 Understanding the plex state cycle ..................................................................... 9 Recovering an unstartable mirrored volume ..................................................
6 Contents Recovering a system by booting from a VxVM root disk mirror ................. 35 Recovering a system by booting from recovery media .................................. 36 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 Initiating VxVM Maintenance Mode Boot ............................................
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.
8 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.
10 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) Initialize plex (vxvol init clean) Start up (vxvol start) Recover data (vxvol resync) PS: CLEAN PKS: DISABLED Shut down (vxvol stop) 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
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.
12 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.
14 Recovery from hardware failure Reattaching failed disks 3 Use the vxdisk list command to verify that the failing flag has been cleared: # vxdisk list DEVICE c1t1d0 c1t2d0 c1t3d0 . . .
Recovery from hardware failure Failures on RAID-5 volumes You can use the command vxreattach -c to check whether reattachment is possible, without performing the operation. Instead, it displays the disk group and disk media name where the disk can be reattached. See the vxreattach(1M) manual page for more information on the vxreattach command. Failures on RAID-5 volumes Failures are seen in two varieties: system failures and disk failures.
16 Recovery from hardware failure Failures on RAID-5 volumes Disk failures An uncorrectable I/O error occurs when disk failure, cabling or other problems cause the data on a disk to become unavailable. For a RAID-5 volume, this means that a subdisk becomes unavailable. The subdisk cannot be used to hold data and is considered stale and detached. If the underlying disk becomes available or is replaced, the subdisk is still considered stale and is not used.
Recovery from hardware failure Failures on RAID-5 volumes V PL SD SV ...
18 Recovery from hardware failure Failures on RAID-5 volumes 2 Any existing log plexes are zeroed and enabled. If all logs fail during this process, the start process is aborted. 3 If no stale subdisks exist or those that exist are recoverable, the volume is put in the ENABLED volume kernel state and the volume state is set to ACTIVE. The volume is now started.
Recovery from hardware failure Failures on RAID-5 volumes Parity resynchronization In most cases, a RAID-5 array does not have stale parity. Stale parity only occurs after all RAID-5 log plexes for the RAID-5 volume have failed, and then only if there is a system failure. Even if a RAID-5 volume has stale parity, it is usually repaired as part of the volume start process.
20 Recovery from hardware failure Failures on RAID-5 volumes configuration database. The -o checkpt=size option controls how often the checkpoint is saved. If the option is not specified, the default checkpoint size is used. Because saving the checkpoint offset requires a transaction, making the checkpoint size too small can extend the time required to regenerate parity.
Recovery from hardware failure Failures on RAID-5 volumes Any failure in the stripes involved in the move makes the volume unusable. The RAID-5 volume can also become invalid if its parity becomes stale.
22 Recovery from hardware failure Failures on RAID-5 volumes Another possible way that a RAID-5 volume can become unstartable is if the parity is stale and a subdisk becomes detached or stale. This occurs because within the stripes that contain the failed subdisk, the parity stripe unit is invalid (because the parity is stale) and the stripe unit on the bad subdisk is also invalid. Figure 1-3 illustrates a RAID-5 volume that has become invalid due to stale parity and a failed subdisk.
Recovery from hardware failure Failures on RAID-5 volumes Forcibly starting RAID-5 volumes You can start a volume even if subdisks are marked as stale: for example, if a stopped volume has stale parity and no RAID-5 logs, and a disk becomes detached and then reattached. The subdisk is considered stale even though the data is not out of date (because the volume was in use when the subdisk was unavailable) and the RAID-5 volume is considered invalid.
24 Recovery from hardware failure Recovering from incomplete disk group moves ■ When all subdisks have been recovered, the volume is placed in the ENABLED kernel state and marked as ACTIVE. It is now started. Recovering from incomplete disk group moves If the system crashes or a subsystem fails while a disk group move, split or join operation is being performed, VxVM attempts either to reverse or to complete the operation when the system is restarted or the subsystem is repaired.
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.
26 Recovery from hardware failure Recovery from failure of a DCO volume vol1_dcl, of vol1 have failed. As a result, the DCO volume, vol1_dcl, of the volume, vol1, has been detached and the state of vol1_dco has been set to BADLOG. For future reference, note 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.
28 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
30 Recovery from failure of instant snapshot operations Failure of vxsnap prepare Failure of vxsnap prepare If a vxsnap prepare operation fails prematurely, the vxprint command may show the new DCO volume in the INSTSNAPTMP state. VxVM can usually recover the DCO volume without intervention. However, in certain situations, this recovery may not succeed.
Recovery from failure of instant snapshot operations Failure of vxsnap make for break-off instant snapshots Failure of vxsnap make for break-off instant snapshots If a vxsnap make operation fails during the creation of a third-mirror break-off instant snapshot, the snapshot volume may go into the INSTSNAPTMP state. VxVM can usually recover the snapshot volume without intervention. However, in certain situations, this recovery may not succeed.
32 Recovery from failure of instant snapshot operations Failure of vxsnap reattach or refresh Failure of vxsnap reattach or refresh If a vxsnap reattach or refresh operation fails, the volume being refreshed may go into the DISABLED state, be marked invalid and be rendered unstartable.
Recovery from failure of instant snapshot operations I/O errors during resynchronization I/O errors during resynchronization Snapshot resynchronization (started by vxsnap syncstart, or by specifying sync=on to vxsnap) stops if an I/O error occurs, and displays the following message on the system console: VxVM vxsnap ERROR V-5-1-6840 Synchronization of the volume volume stopped due to I/O error After correcting the source of the error, use the following command to restart the resynchronization operation: #
34 Recovery from failure of instant snapshot operations I/O failure on a DCO volume
Chapter 3 Recovering from boot disk failure VxVM and boot disk failure Veritas Volume Manager (VxVM) protects systems from disk and other hardware failures and helps you to recover from such events. Recovery procedures help to prevent loss of data or system access due to the failure of the boot (root) disk. The procedures for recovering volumes and their data on boot disks differ from the procedures that are used for non-boot disks. See “Recovery from hardware failure” on page 7.
36 Recovering from boot disk failure Recovering a system by booting from recovery media 2 Boot the system from a mirror of the root disk, and use the vxrootmir command to initialize and mirror the volumes on the new root disk: # /etc/vx/bin/vxrootmir -v -b new_root_disk_access_name The -b option sets the newly mirrored disk as the alternate boot disk in the NVRAM. The -v option gives progress indications as each volume is being mirrored.
Recovering from boot disk failure Recovering a system 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.
38 Recovering from boot disk failure Initiating VxVM Maintenance Mode Boot 3 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 time if the /etc/vx/volboot file is missing or its contents are incorrect: vxvm:vxconfigd: ERROR: enable failed: Volboot file not loaded transactions are disabled.
Recovering from boot disk failure Recovery by reinstallation Warning: 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.
40 Recovering 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 (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.
42 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 Note: The client ID is the same as that recorded for the corresponding transactions in the transactions log. See “Logging transactions” on page 44 and “Associating command and transaction logs” on page 46 for more information. Most command scripts are not logged, but the command binaries that they call are logged. Exceptions are the vxdisksetup, vxinstall, and vxdiskunsetup scripts, which are logged.
44 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 Each log file contains a header that records the host name, host ID, and the date and time that the log was created.
46 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.
48 Backing up and restoring disk group configurations Backing up a disk group configuration Errors in some configuration copies Format error in configuration copy 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 corr
Backing up and restoring disk group configurations Restoring a disk group configuration Here diskgroup is the name of the disk group, and dgid is the disk group ID. If a disk group is to be recreated on another system, copy these files to that system. Caution: Take care that you do not overwrite any files on the target system that are used by a disk group on that system.
50 Backing up and restoring disk group configurations Restoring a disk group configuration At the precommit stage, you can use the vxprint command to examine the configuration that the restored disk group will have. You can choose to proceed to commit the changes and restore the disk group configuration. Alternatively, you can cancel the restoration before any permanent changes have been made.
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 . . .
52 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 (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 kernel driver, vxio. These include some errors that are infrequently encountered and difficult to troubleshoot. Note: Some error messages described here may not apply to your system.
54 Error messages Logging error messages Note: syslog logging is enabled by default. Debug message logging is disabled by default. 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.
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.
56 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.
58 Error messages Understanding messages Note: This message may also appear during a plex detach operation in a cluster. In this case, no action is required. 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.
Error messages Understanding messages V-5-0-108 VxVM vxio WARNING V-5-0-108 Device major, minor: Received spurious close ■ Description: 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. ■ Action: No action is necessary; the system will continue.
60 Error messages Understanding messages V-5-0-144 VxVM vxio WARNING V-5-0-144 Double failure condition detected on RAID-5 volume ■ ■ Description: I/O errors have been received in more than one column of a RAID-5 volume. This could be caused by: ■ a controller failure making more than a single drive unavailable ■ the loss of a second drive while running in degraded mode ■ two separate disk drives failing simultaneously (unlikely) Action: Correct the hardware failures if possible.
Error messages Understanding messages V-5-0-148 VxVM vxdmp NOTICE V-5-0-148 enabled path path_device_number belonging to dmpnode dmpnode_device_number ■ Description: 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. ■ Action: None.
62 Error messages Understanding messages group. The log re-initializes on the new drive. Finally force the failed volume into an active state and recover the data. V-5-0-168 VxVM vxio WARNING V-5-0-168 Failure in RAID-5 logging operation ■ Description: Indicates that a RAID-5 log has failed. ■ Action: To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume.
Error messages Understanding messages ■ Action: To restore RAID-5 logging to a RAID-5 volume, create a new log plex and attach it to the volume. V-5-0-216 VxVM vxio WARNING V-5-0-216 mod_install returned errno ■ Description: A call made to the operating system mod_install function to load the vxio driver failed. ■ Action: Check for additional console messages that may explain why the load failed.
64 Error messages Understanding messages V-5-0-249 VxVM vxio WARNING V-5-0-249 RAID-5 volume entering degraded mode operation ■ Description: 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.
Error messages Understanding messages ■ Action: None; 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.
66 Error messages Understanding messages V-5-1-92 VxVM vxconfigd WARNING V-5-1-92 Cannot exec /usr/bin/rm to remove directory: reason ■ Description: 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.
Error messages Understanding messages V-5-1-117 VxVM vxconfigd ERROR V-5-1-117 Cannot start volume volume, no valid plexes ■ Description: This error indicates that the volume cannot be started because it does not contain any valid plexes. This can happen, for example, if disk failures have caused all plexes to be unusable.
68 Error messages Understanding messages V-5-1-123 VxVM vxconfigd ERROR V-5-1-123 Disk group group: Disabled by errors ■ Description: 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.
Error messages Understanding messages V-5-1-135 VxVM vxconfigd FATAL ERROR V-5-1-135 Memory allocation failure during startup ■ Description: This implies that there is insufficient memory to start up VxVM. ■ Action: 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.
70 Error messages Understanding messages package. If you cannot re-add the package, contact Veritas Technical Support for more information. VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/fstab: reason ■ Description: vxconfigd could not open the /etc/fstab file, for the reason given. The /etc/fstab file is used to determine which volume (if any) to use for the /usr file system. ■ Action: This error implies that your root file system is currently unusable.
Error messages Understanding messages V-5-1-484 VxVM vxconfigd ERROR V-5-1-484 Cannot start volume volume, no valid complete plexes ■ Description: 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.
72 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 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 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.
74 Error messages Understanding messages ■ Action: 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. 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 host ID for the system.
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.
76 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 autoimporting 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 ■ Action: 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.
78 Error messages Understanding messages V-5-1-587 VxVM vxdg ERROR V-5-1-587 disk group reason groupname: import failed: ■ Description: The import of a disk group failed for the specified reason. ■ Action: 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.
Error messages Understanding messages Caution: Be careful when using the -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.
80 Error messages Understanding messages V-5-1-737 VxVM vxconfigd ERROR V-5-1-737 Mount point path: volume not in bootdg disk group ■ Description: The volume device listed in the /etc/fstab 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.
Error messages Understanding messages V-5-1-923 VxVM vxplex ERROR V-5-1-923 Record volume is in disk group diskgroup1 plex is in group diskgroup2. ■ Description: An attempt was made to snap back a plex from a different disk group. ■ Action: Move the snapshot volume into the same disk group as the original volume.
82 Error messages Understanding messages ■ Action: In case 1, 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/fstab file to correct the entry for the /usr file system.
Error messages Understanding messages 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. Additionally, this may be followed with: VxVM vxconfigd ERROR V-5-1-579 Disk group group: Errors in some configuration copies: Disk device, copy number: Block bno: error ...
84 Error messages Understanding messages V-5-1-2197 VxVM vxconfigd ERROR V-5-1-2197 node N: missing vxconfigd ■ Description: The vxconfigd daemon is not running on the indicated cluster node. ■ Action: Restart the vxconfigd daemon. 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 V-5-1-2353 VxVM vxconfigd ERROR V-5-1-2353 Disk group group: Cannot recover temp database: reason Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)]. ■ Description: This can happen if you kill and restart vxconfigd, or if you disable and enable it with vxdctl disable and vxdctl enable. This error indicates a failure related to reading the file /var/vxvm/tempdb/ group.
86 Error messages Understanding messages V-5-1-2824 VxVM vxconfigd ERROR V-5-1-2824 Configuration daemon error 242 ■ Description: 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. ■ Action: No action is necessary if the join is slow or a retry eventually succeeds.
Error messages Understanding messages V-5-1-2862 VxVM vxdg ERROR V-5-1-2862 object: Operation is not supported ■ Description: DCO and snap objects dissociated by Persistent FastResync, and VVR objects cannot be moved between disk groups. ■ Action: None. The operation is not supported.
88 Error messages Understanding messages ■ Action: Use the correct name, or import the disk group and try again. V-5-1-2908 VxVM vxdg ERROR V-5-1-2908 diskdevice: Request crosses disk group boundary ■ Description: The specified disk device is not configured in the source disk group for a disk group move or split operation. ■ Action: Correct the name of the disk object specified in the disk group move or split operation.
Error messages Understanding messages ■ Action: None. The operation is not supported. V-5-1-2935 VxVM vxassist ERROR V-5-1-2935 No more space in disk group configuration. ■ Description: There is no more space in the disk group’s configuration database for VxVM object records. ■ Action: 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.
90 Error messages Understanding messages V-5-1-3023 VxVM vxconfigd ERROR V-5-1-3023 Disk in use by another cluster ■ Description: An attempt was made to import a disk group whose disks are stamped with the ID of another cluster. ■ Action: If the disk group is not imported by another cluster, retry the import using the -C (clear import) flag. V-5-1-3024 VxVM vxconfigd ERROR V-5-1-3024 vxclust not there ■ Description: An error during an attempt to join a cluster caused vxclust to fail.
Error messages Understanding messages ■ Action: 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).
92 Error messages Understanding messages V-5-1-3046 VxVM vxconfigd ERROR V-5-1-3046 Node activation conflict ■ Description: The disk group could not be activated because it is activated in a conflicting mode on another node in a cluster. ■ Action: Retry later, or deactivate the disk group on conflicting nodes. V-5-1-3049 VxVM vxconfigd ERROR V-5-1-3049 Retry rolling upgrade ■ Description: An attempt was made to upgrade a cluster to a higher protocol version when a transaction was in progress.
Error messages Understanding messages V-5-1-3243 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. ■ Description: The vxdmpadm start restore command has been executed while the restore daemon is already running. ■ Action: Stop the restore daemon and restart it with the required set of parameters as shown in the vxdmpadm(1M) manual page.
94 Error messages Understanding messages V-5-1-3828 VxVM vxconfigd ERROR V-5-1-3828 upgrade operation failed: Already at highest version ■ Description: An upgrade operation has failed because a cluster is already running at the highest protocol version supported by the master. ■ Action: No further action is possible as the master is already running at the highest protocol version it can support.
Error messages Understanding messages V-5-1-4267 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. ■ Description: 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.
96 Error messages Understanding messages ■ Action: 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): salcontact=no V-5-1-4625 VxVM vxassist WARNING V-5-1-4625 SAL authentication failed...
Error messages Understanding messages 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. V-5-1-5929 VxVM vxconfigd NOTICE V-5-1-5929 Unable to resolve duplicate diskid. ■ Description: VxVM has detected disks with duplicate disk identifiers.
98 Error messages Understanding messages 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 c2t66d0 and c2t67d0: # vxdisk updateudid c2t66d0 c2t67d0 ■ Case 3: If DMP has been disabled to an array that has multiple paths, then each path to the array is claimed as a unique disk. If DMP is suppressed, VxVM does not know which path to select as the true path. You must choose which path to use.
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.
100 Index E emergency startup 37 EMPTY plex state 9 ENABLED plex kernel state 9 ENABLED volume kernel state 18 ERROR messages 56 error messages A virtual disk device is open 70 All transactions are disabled 68 Already at highest version 94 Attempt to disable controller failed 93 Attempt to enable a controller that is not available 84 can’t import diskgroup 94 Can’t locate disk(s) 95 Cannot assign minor 90 Cannot auto-import group 47, 75 Cannot find disk on slave node 89 Cannot kill existing daemon 83 canno
Index some subdisks are unusable and the parity is stale 22 startup script 54 Synchronization of the volume stopped due to I/O error 33 System startup failure 69 The VxVM restore daemon is already running 93 There are two backups that have the same diskgroup name with different diskgroup id 50 Transaction already in progress 86 transactions are disabled 38 Unable to add portal for cluster 90 Unrecognized operating mode 65 update failed 68 upgrade operation failed 94 Version number of kernel does not match
102 Index Detached disk 67 Detached log for volume 71 Detached plex in volume 71 Detached subdisk in volume 72 Detached volume 72 disabled controller connected to disk array 59 disabled dmpnode 59 disabled path belonging to dmpnode 59 enabled controller connected to disk array 60 enabled dmpnode 60 enabled path belonging to dmpnode 61 Offlining config copy 80 Path failure 63 read error on object 64 removed disk array 65 Rootdisk has just one enabled path 58 Unable to resolve duplicate diskid 97 Volume ente
Index reinstalling 39 system failures 15 T transactions associating with commands 46 logging 44 translog file 44 TUTIL0 field clearing MOVE flag 24 U udid_mismatch flag 97 V V-5-0-106 58 V-5-0-108 59 V-5-0-110 59 V-5-0-111 59 V-5-0-112 59 V-5-0-144 60 V-5-0-145 60 V-5-0-146 60 V-5-0-147 60 V-5-0-148 61 V-5-0-164 61 V-5-0-166 61 V-5-0-168 62 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 63 V-5-0-237 63 V-5-0-243 63 V-5-0-244 63 V-5-0-249 64 V-5-0-251 64 V-5-0-252 64 V-5-0-258 6
104 Index V-5-1-3032 91 V-5-1-3033 91 V-5-1-3034 91 V-5-1-3042 91 V-5-1-3046 92 V-5-1-3049 92 V-5-1-3050 92 V-5-1-3091 92 V-5-1-3212 92 V-5-1-3243 93 V-5-1-3362 93 V-5-1-3486 93 V-5-1-3689 93 V-5-1-3828 94 V-5-1-3848 94 V-5-1-4220 94 V-5-1-4267 95 V-5-1-4277 95 V-5-1-4551 95 V-5-1-4620 95 V-5-1-4625 96 V-5-1-480 70 V-5-1-484 71 V-5-1-5150 96 V-5-1-5160 96 V-5-1-5161 96 V-5-1-5162 97 V-5-1-525 71 V-5-1-526 71 V-5-1-527 72 V-5-1-528 72 V-5-1-543 72 V-5-1-544 72 V-5-1-545 73 V-5-1-546 73 V-5-1-554 73 V-5-1-55
Index displaying volume and plex states 8 vxreattach reattaching failed disks 14 vxsnap make recovery from failure of 30 vxsnap prepare recovery from failure of 30 vxsnap reattach recovery from failure of 32 vxsnap refresh recovery from failure of 32 vxsnap restore recovery from failure of 31 vxtranslog controlling transaction logging 44 VxVM emergency startup 37 RAID-5 recovery process 17 starting after booting from recovery media 37 using Maintenance Mode Boot (MMB) 38 vxvol recover command 20 vxvol resy
106 Index
