VERITAS Volume Manager 3.5 Troubleshooting Guide VERITAS Volume Manager 3.
Legal Notices Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
Contents 1. Recovery from Hardware Failure Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the Plex State Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Unstartable Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents vxdmpadm Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 vxplex Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Cluster Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Introduction The VERITAS Volume Manager Troubleshooting Guide provides information about how to recover from hardware failure, and how to understand and deal with Veritas Volume Manager (VxVM) error messages during normal operation. For detailed information about VERITAS Volume Manager and how to use it, refer to the VERITAS Volume Manager Administrator’s Guide.
• VERITAS Volume Manager manual pages Conventions The following table describes the typographic conventions used in this guide. Typeface Usage Examples Computer output, file contents, files, directories, software elements such as command options, function names, and parameters Read tunables from the /etc/vx/tunefstab file. New terms, book titles, emphasis, variables to be replaced by a name or value See the User’s Guide for details.
• U.S. and Canadian Customers: 1-800-342-0652 • International Customers: +1 (650) 527-8555 • Email: support@veritas.com For license information (U.S. and Canadian Customers): • Phone: 1-925-931-2464 • Email: license@veritas.com • Fax: 1-925-931-2487 For software updates: • Email: swupdate@veritas.com For information on purchasing VERITAS products: • Phone: 1-800-258-UNIX (1-800-258-8649) or 1-650-527-8000 • Email: vx-sales@veritas.
1 Chapter 1 Recovery from Hardware Failure 9
Recovery from Hardware Failure Introduction Introduction Veritas 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 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 firm understanding of the various plex states and their interrelationship is necessary if you want to be able to perform the recovery procedure described in this chapter. The Figure 1-1, “Main Plex State Cycle,” shows the main transitions that take place between plex states in VxVM.
Recovery from Hardware Failure Understanding the Plex State Cycle When first created, a plex has state EMPTY until the volume to which it is attached is initialized. Its state is then set to CLEAN. Its plex kernel state remains set to DISABLED and is not set to ENABLED until the volume is started. Figure 1-2 Additional Plex State Transitions After a system crash and reboot, all plexes of a volume are ACTIVE but marked with plex kernel state DISABLED until their data is recovered by the vxvol resync task.
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 Restarting a Disabled Volume Restarting a Disabled Volume If a disk failure caused a volume to be disabled, you must restore the volume from a backup after replacing the failed disk. Any volumes that are listed as Unstartable must be restarted using the vxvol command before restoring their contents from a backup.
Recovery from Hardware Failure Recovering a Mirrored Volume Recovering a 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. You can mark one of the plexes CLEAN and instruct the system to use that plex as the source for reviving the others as follows: Step 1.
Recovery from Hardware Failure Reattaching Disks Reattaching Disks You can perform a reattach operation if a disk fails completely and hot-relocation is not possible, or if VxVM is started with some disk drivers unloaded and unloadable (causing disks to enter the failed state). If the underlying problem has been fixed, you can use the vxreattach command to reattach the disks without plexes being flagged as STALE. However, the reattach must occur before any volumes on the disk are started.
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 reconstructing-read. 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 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. Whenever a volume is started, any RAID-5 log plexes are zeroed before the volume is started. This prevents random data from being interpreted as a log entry and corrupting the volume contents.
Recovery from Hardware Failure Failures on RAID-5 Volumes If hot-relocation is enabled at the time of a disk failure, system administrator intervention is not required unless no suitable disk space is available for relocation. Hot-relocation is triggered by the failure and the system administrator is notified of the failure by electronic mail. Hot relocation automatically attempts to relocate the subdisks of a failing RAID-5 plex.
Recovery from Hardware Failure Failures on RAID-5 Volumes option. If the -o iosize option is not specified, the default maximum I/O size is used. The resync operation then moves onto the next region until the entire length of the RAID-5 volume has been resynchronized. For larger volumes, parity regeneration can take a long time. It is possible that the system could be shut down or crash before the operation is completed.
Recovery from Hardware Failure Failures on RAID-5 Volumes • the RAID-5 volume is stopped but was not shut down cleanly; that is, the parity is considered stale • the RAID-5 volume is active and has no valid log areas Only the third case can be overridden by using the -o force option. Subdisks of RAID-5 volumes can also be split and joined by using the vxsd split command and the vxsd join command. These operations work the same way as those for mirrored volumes.
Recovery from Hardware Failure Failures on RAID-5 Volumes Figure 1-3 Invalid RAID-5 Volume 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. This qualifies as two failures within a stripe and prevents the use of the volume.
Recovery from Hardware Failure Failures on RAID-5 Volumes This is done because if the system were to crash or the volume was ungracefully stopped while it was active, the parity becomes stale, making the volume unusable. If this is undesirable, the volume can be started with the -o unsafe start option. CAUTION The -o unsafe start option is considered dangerous, as it can make the contents of the volume unusable. It is therefore not recommended.
Recovery from Hardware Failure Recovering from Incomplete Disk Group Moves 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. Whether the operation is reversed or completed depends on how far it had progressed.
Recovery from Hardware Failure Recovery from DCO Volume Failure Recovery from DCO Volume Failure Persistent FastResync uses a data change object (DCO) log 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. (You can use one of the options -a, -F or -m to vxprint to check if the badlog flag is set on a DCO.) All further writes to the volume are not tracked by the DCO.
Recovery from Hardware Failure Recovery from DCO Volume Failure NOTE You cannot use vxassist snapback because the snapclear operation removes the snapshot association information.
Recovery from Hardware Failure Recovery from DCO Volume Failure 28 Chapter 1
2 Chapter 2 Recovery from Boot Disk Failure 29
Recovery from Boot Disk Failure Introduction Introduction NOTE Rootability, which brings the root disk under Veritas Veritas Volume Manager control, is supported in this release of VxVM on HP-UX 11i. Veritas 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.
Recovery from Boot Disk Failure Recovery from a Failed VxVM Boot Mirror Disk Recovery from a Failed VxVM Boot Mirror Disk If a failed primary boot disk is under VxVM control and is mirrored, follow these steps to replace it: Step 1. Replace the failed boot disk. Depending on the system hardware, this may require you to shut down and power off the system. Step 2.
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, 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 installation CD. • Bootable recovery tape. • Secondary boot disk in the configuration. • HP-UX Ignite-UX server that is accessible over a LAN.
Recovery from Boot Disk Failure Recovery by Booting from Recovery Media ... v root DISABLED ... pl rootvol DISABLED ... sd rootvol-01 ENABLED 0 ... pl rootvol 393216 STALE sd rootvol-02 ENABLED 0 ... rootvol 393216 ACTIVE rootvol-01 393216 STALE rootdisk01-02 393216 rootvol-02 DISABLED ... rootdisk02-02 393216 - When this happens, the root volume can usually be repaired by using the following command: # vxvol -g rootdg -f start rootvol If the root volume is mirrored, recovery is started.
Recovery from Boot Disk Failure Recovery by Booting from Recovery Media Error returned from vxconfigd -m boot, halting • Description: During system bootup, the VxVM configuration daemon reads the file /etc/vx/volboot. If that file is missing or corrupted, the configuration daemon fails and aborts the boot sequence. • Action: Reboot from recovery media and run the following command: # vx_emerg_start -m hostname This determines if the volboot file is present, and rewrites it if it is not present.
Recovery from Boot Disk Failure Using VxVM Maintenance Mode Boot (MMB) Using VxVM Maintenance Mode Boot (MMB) Another method for performing limited recovery on a VxVM boot disk is to use the VxVM Maintenance Mode Boot (MMB). MMB mode is initiated by booting the system and gaining control at the ISL prompt.
Recovery from Boot Disk Failure Using VxVM Maintenance Mode Boot (MMB) Step 5.
Recovery from Boot Disk Failure Recovery by Reinstallation Recovery by Reinstallation NOTE If you configured VxVM rootability by installing via Ignite-UX, consult the “System Recovery” section of the Ignite-UX Administration Guide, before consulting this section. In many instances, reinstalling from a saved Ignite-UX configuration is sufficient to recover a failed boot disk.
Recovery from Boot Disk Failure Recovery by Reinstallation Reinstalling the System and Recovering VxVM To reinstall the system and recover the Veritas Veritas Volume Manager configuration, use the following procedure. These steps are described in detail in the sections that follow: Step 1. “Prepare the System for Reinstallation” on page 38. Replace any failed disks or other hardware, and detach any disks not involved in the reinstallation. Step 2. “Reinstall the Operating System” on page 38.
Recovery from Boot Disk Failure Recovery by Reinstallation Reinstall VxVM To reinstall Veritas Volume Manager, follow these steps: Step 1. Load Veritas Volume Manager from CD-ROM. Follow the instructions in the VERITAS Volume Manager Installation Guide. CAUTION To reconstruct the Volume Manager configuration that remains on the non-root disks, do not use vxinstall to initialize VxVM after loading the software from CD-ROM. Step 2.
Recovery from Boot Disk Failure Recovery by Reinstallation The configuration preserved on the disks not involved with the reinstallation has now been recovered. However, because the root disk has been reinstalled, it does not appear to VxVM as a VM disk. The configuration of the preserved disks does not include the root disk as part of the VxVM configuration.
Recovery from Boot Disk Failure Recovery by Reinstallation disk03 online - rootdg rootdg disk01 failed was:c0t0d0 NOTE Your system may use a device name that differs from the examples. For more information on device names, see the chapter “Administering Disks” in the VERITAS Volume Manager Administrator’s Guide. The display shows that the reinstalled root device, c0t0d0, is not associated with a VM disk and is marked with a status of error.
Recovery from Boot Disk Failure Recovery by Reinstallation v v01 DISABLED 24000 pl v01-01 DISABLED 24000 sd disk01-06 disk01 24000 c1t5d1 fsgen ACTIVE SELECT v01 NODEVICE CONCAT RW v0101 245759 0 ENA The only plex of the volume is shown in the line beginning with pl. The STATE field for the plex named v01-01 is NODEVICE. The plex has space on a disk that has been replaced, removed, or reinstalled. The plex is no longer valid and must be removed. Step 4.
Recovery from Boot Disk Failure Recovery by Reinstallation c1t5d2 sd disk01 10240 ENA v02-01 620544 1/0 disk01-05 c1t5d3 sd disk03-01 disk03 10240 c1t5d4 DIS v02-01 620544 2/0 ENA The display shows three disks, across which the plex v02-01 is striped (the lines starting with sd represent the stripes). One of the stripe areas is located on a failed disk. This disk is no longer valid, so the plex named v02-01 has a state of NODEVICE.
Recovery from Boot Disk Failure Recovery by Reinstallation sd disk03 30720 RW disk01-04 v03-02 262144 0 c1t5d6 DIS This volume has two plexes, v03-01 and v03-02. The first plex (v03-01) does not use any space on the invalid disk, so it can still be used. The second plex (v03-02) uses space on invalid disk disk01 and has a state of NODEVICE. Plex v03-02 must be removed. However, the volume still has one valid plex containing valid data. If the volume needs to be mirrored, another plex can be added later.
Recovery from Boot Disk Failure Recovery by Reinstallation The final step is to start up hot-relocation, if this is required. Start up Hot-Relocation To start up the hot-relocation service, either reboot the system or manually start the relocation watch daemon, vxrelocd (this also starts the vxnotify process). NOTE Hot-relocation should only be started when you are sure that it will not interfere with other reconfiguration procedures.
Recovery from Boot Disk Failure Recovery by Reinstallation 46 Chapter 2
3 Chapter 3 Error Messages 47
Error Messages Introduction Introduction 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.
Error Messages Logging Error Messages Logging Error Messages VxVM provides the option of logging console output to a file. This logging is useful in that any messages output just before a system crash will be available in the log file (presuming that the crash does not result in file system corruption). vxconfigd controls whether such logging is turned on or off. If enabled, the default log file is /var/adm/configd.log. vxconfigd also supports the use of syslog to log all of its regular console messages.
Error Messages Configuring Logging in the Startup Script Configuring Logging in the Startup Script To enable log file or syslog logging, you can edit the following portion of the /sbin/init.d/vxvm-sysboot script that starts the VxVM configuration daemon, vxconfigd: # comment-out or uncomment any of the following lines to enable or # disable the corresponding feature in vxconfigd. #opts=”$opts -x syslog” # use syslog for console messages #opts=”$opts -x log” # messages to vxconfigd.
Error Messages Understanding Error Messages Understanding Error Messages VxVM is fault-tolerant and resolves most problems without system administrator intervention. If the configuration daemon (vxconfigd) recognizes the actions that are necessary, it queues up the transactions that are required. VxVM provides atomic changes of system configurations; either a transaction completes fully, or the system is left in the same state as though the transaction was never attempted.
Error Messages Kernel Panic Messages Kernel Panic Messages A panic is a severe event as it halts a system during its normal operation. A panic message from the kernel indicates the nature of the hardware problem or software inconsistency that is so severe that the system cannot continue. The operating system may also provide a dump of the CPU register contents and a stack trace to aid in identifying the cause of the panic.
Error Messages Kernel Warning Messages Kernel Warning Messages A warning message from the kernel indicates that a non-critical operation has failed, possibly because some resource is not available. Corrective action should be taken immediately. vxvm:vxio:WARNING: Cannot find device number for boot_path • Description: The boot path retrieved from the system PROMs cannot be converted to a valid device number. • Action: Check your PROM settings for the correct boot string.
Error Messages Kernel Warning Messages • Action: 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 add a new DRL log to the volume.
Error Messages Kernel Warning Messages • 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. Also check the console messages log file for any additional messages that were logged but not displayed on the console.
Error Messages Kernel Warning 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. 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 (see the vxevac (1M) manual page) and then to reformat the drive.
Error Messages Kernel Notice Messages Kernel Notice Messages A notice message indicates that an error has occurred that should be monitored. Shutting down the system is unnecessary, although you may need to take action to remedy the fault at a later date. vxvm:vxio:NOTICE: Can’t close disk disk in group disk_group. If it is removable media (like a floppy), it may have been removed. Otherwise, there may be problems with the drive.
Error Messages vxassist Error Messages vxassist Error Messages An error message from the vxassist command indicates that the requested operation cannot be performed. Follow the recommended course of action given below. vxvm:vxassist: ERROR: Insufficient number of active snapshot mirrors in snapshot_volume. • Description: An attempt to snap back a specified number of snapshot mirrors to their original volume failed.
Error Messages vxassist Warning Messages vxassist Warning Messages A warning message from the vxassist command indicates a problem with its operation. Action should be taken to correct the problem as soon as possible. Follow the recommended course of action given below. vxvm:vxassist: WARNING: 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.
Error Messages vxconfigd Fatal Error Messages vxconfigd Fatal Error Messages A fatal error message from the configuration daemon, vxconfigd, indicates a severe problem with the operation of VxVM that prevents it from running.
Error Messages vxconfigd Error Messages vxconfigd Error Messages An error message from the configuration daemon, vxconfigd, indicates a problem with the operation of VxVM that may prevent it from running effectively. Action should be taken to correct the problem immediately.
Error Messages vxconfigd Error Messages • Description: 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.
Error Messages vxconfigd Error Messages • Description: These errors indicate that the volume cannot be started because the volume contains no 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).
Error Messages vxconfigd Error Messages vxvm:vxconfigd: ERROR: 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. The error indicates that one of the disks in a disk group could not be updated with the new host ID. Most likely, this indicates that the given disk has become inaccessible or has failed in some other way.
Error Messages vxconfigd Error Messages If the disk group that was disabled is the rootdg disk group, then the following additional error is displayed: vxvm:vxconfigd: ERROR: 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 rootdg.
Error Messages vxconfigd Error Messages vxvm:vxconfigd: ERROR: Disk group group, Disk disk: Group name collides with record in rootdg • Description: The name of a disk group that is being imported conflicts with the name of a record in the rootdg disk group. VxVM does not allow this kind of conflict because of the way the /dev/vx/dsk directory is organized: devices corresponding to records in the root disk group share this directory with subdirectories for each disk group.
Error Messages vxconfigd Error Messages • Description: 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. • Action: A major cause for this kind of failure is disk failures that were not addressed before vxconfigd was stopped or disabled.
Error Messages vxconfigd Error Messages Evaluate the error messages to determine the root cause of the problem. Make changes suggested by the errors and then try rerunning the command. vxvm:vxconfigd: ERROR: Failed to store commit status list into kernel: reason vxvm:vxconfigd: ERROR: GET_VOLINFO ioctl failed: reason vxvm:vxconfigd: ERROR: Get of current rootdg failed: reason • Description: These internal errors should not occur unless there is a bug in VxVM. • Action: Contact Customer Support.
Error Messages vxconfigd Error Messages • Description: An open failed for /dev/vx/dsk, /dev/vx/rdsk, or one of their subdirectories. The only likely cause of such a failure is that the directory was removed by the administrator or by an errant program. If this is the case, the reason should be “No such file or directory.” An alternate possible cause is an I/O failure. • Action: If the reason was “No such file or directory,” use mkdir to recreate the directory. Then run the command vxdctl enable.
Error Messages vxconfigd Error Messages • Action: Reboot the system. If that does not cure the problem, re-add the VxVM packages. vxvm:vxconfigd:ERROR:volume_name:vxconfigd cannot boot-start RAID-5 volumes • Description: 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.
Error Messages vxconfigd Warning Messages vxconfigd Warning Messages A warning message from the configuration daemon, vxconfigd, indicates a problem that may affect the operation of VxVM. Action should be taken to correct the problem as soon as possible. vxvm:vxconfigd: WARNING: Bad request number: client number, portal [REQUEST|DIAG], size number • Description: This diagnostic message indicates that a utility sent an invalid request to vxconfigd.
Error Messages vxconfigd Warning Messages • Description: This problem usually occurs only if there is a bug in VxVM. However, it may also occur if memory is low. • Action: Contact Customer Support. vxvm:vxconfigd: WARNING: Cannot open log file log_filename: reason • Description: The vxconfigd console output log file could not be opened for the given reason. • Action: Create any needed directories, or use a different log file path name as described in “Logging Error Messages” on page 49.
Error Messages vxconfigd Warning Messages 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.
Error Messages vxconfigd Warning Messages • Description: 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 3.5 host ID. This warning message should result only from a vxdctl hostid operation. • Action: Typically, unless a disk group was disabled due to transient errors, there is no way to repair a disabled disk group.
Error Messages vxconfigd Warning Messages • Action: Use the vxdg reminor command to renumber all volumes in the offending disk group permanently. See the vxdg(1M) manual page for more information. vxvm:vxconfigd: WARNING: Internal transaction failed: reason • Description: This problem usually occurs only if there is a bug in VxVM. However, it may also occur if memory is low. • Action: Contact Customer Support.
Error Messages vxconfigd Notice Messages vxconfigd Notice Messages A notice message from the configuration daemon, vxconfigd, indicates that VxVM has taken some action that you may wish to monitor. Action should be taken to correct any associated hardware problem as soon as possible. vxvm:vxconfigd: NOTICE: Detached disk disk • Description: The named disk appears to have become unusable and was detached from its disk group.
Error Messages vxconfigd Notice Messages • Description: 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. • Action: 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.
Error Messages vxconfigd Notice Messages — Case 3: If disks have become duplicated using the dd command or any other disk copying utility, choose which set of duplicate disks you want to exclude, and then either edit the file /etc/vx/vxvm.exclude, or, if vxconfigd is running, 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).
Error Messages vxdg Error Messages vxdg Error Messages An error message from the vxdg command indicates that the requested operation cannot be performed. Follow the recommended course of action given below. vxvm: vxdg: ERROR: diskgroup: Cannot remove last disk group configuration copy • Description: The requested disk group move, split or join operation would leave the disk group without any configuration copies. • Action: None. The operation is not supported.
Error Messages vxdg Error Messages • Action: Objects specified for a disk group move, split or join must be either disks or top-level volumes. vxvm: vxdg: ERROR: 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 vxdmp Notice Messages vxdmp Notice Messages A notice message from the Dynamic Multipathing (DMP) driver, vxdmp, indicates that it has taken some action that you may wish to monitor. Action should be taken to correct any associated hardware problem as soon as possible. vxvm:vxdmp:NOTICE:added disk array disk_array_serial_number • Description: A new disk array has been added to the host. • Action: None. vxvm:vxdmp:NOTICE:Attempt to disable controller controller_name failed.
Error Messages vxdmp Notice Messages • NOTE Action: Check the underlying hardware if you want to recover the desired path. vxvm:vxdmp:NOTICE:enabled controller controller_name connected to disk array disk_array_serial_number • Description: All paths through the controller connected to the disk array are enabled. This usually happens if a controller is enabled after maintenance. • Action: None.
Error Messages vxdmpadm Error Messages vxdmpadm Error Messages An error message from the Dynamic Multipathing (DMP) administration utility, vxdmpadm, indicates a problem with the requested DMP operation. vxvm:vxdmpadm: ERROR: 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. • Description: Disabling the controller could lead to some devices becoming inaccessible.
Error Messages vxplex Error Messages vxplex Error Messages An error message from the plex administration utility, vxplex, indicates a problem with the requested operation. vxvm:vxplex: ERROR: Plex plex not associated with a snapshot volume. • Description: An attempt was made to snap back a plex that is not from a snapshot volume. • Action: Specify a plex from a snapshot volume. vxvm:vxplex: ERROR: Plex plex not attached. • Description: An attempt was made to snap back a detached plex.
Error Messages Cluster Error Messages Cluster Error Messages This section lists error messages that may occur with VxVM in a cluster environment. Some of these messages may appear on the console; others are returned by vxclust. Cannot assign minor minor • Description: A slave attempted to join, but an existing volume on the slave has the same minor number as a shared volume on the master.
Error Messages Cluster Error Messages • Description: An attempt was made to online a disk whose controller has been reserved by another host. • Action: No action is necessary. The cluster manager frees the disk and VxVM puts it online when the node joins the cluster. 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).
Error Messages Cluster Error Messages • Description: 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 a programming error. • Action: Contact Customer Support. Missing vxconfigd • Description: The vxconfigd daemon is not running. • Action: Restart the vxconfigd daemon.
Error Messages Cluster Error Messages This node was running different CM. Please Reboot. • Description: VxVM supports clustering under the control of various cluster managers. However, once a node joins the cluster under a particular cluster manager, it cannot be restarted under a different cluster manager until it is rebooted. • Action: Reboot the host machine if the cluster must be started under a different cluster manager.
Error Messages Cluster Error Messages • Description: An error during an attempt to join the cluster caused vxclust to fail. This may be caused by the failure of another node during a join or by the failure of vxclust. • Action: Retry the join. An error message on the other node may clarify the problem. vxiod count must be above number to join cluster • Description: The number of 3.5 kernel daemons (vxiod) is less than the minimum number needed to join the cluster.
Error Messages Cluster Error Messages 90 Chapter 3
