Home > Veritas Storage Foundation™ Volume Manager Manual Pages
vxrelocd root &
and you want mail also to be sent to user1 and user2, change the line to read:
vxrelocd root user1 user2 &
Alternatively, you can kill the vxrelocd process and restart it as vxrelocd root mail_address, where mail_address is a user's login name. Do not kill the vxrelocd process while a relocation attempt is in progress.
The mail notification that is sent when a failure is detected follows this format:
medianame ... failed plexes: plexname ... failed log plexes: plexname ... failing disks: medianame ... failed subdisks: subdiskname ... The Volume Manager will attempt to find spare disks, relocate failed subdisks and then recover the data in the failed plexes.Failures have been detected by the Veritas Volume Manager: failed disks:
The medianame list under failed disks specifies disks that appear to have completely failed; the medianame list under failing disks indicates a partial disk failure or a disk that is in the process of failing. When a disk has failed completely, the same medianame list appears under both failed disks and failing disks. The plexname list under failed plexes shows plexes that were detached due to I/O failures that occurred while attempting to do I/O to subdisks they contain. The plexname list under failed log plexes indicates RAID-5 or DRL (dirty region logging) log plexes that have failed. The subdiskname list specifies subdisks in RAID-5 volumes that were detached due to I/O errors.
To determine which of the eligible disks to use, vxrelocd first tries the disk that is closest to the failed disk. The value of ``closeness'' depends on the controller and disk number of the failed disk. A disk on the same controller as the failed disk is closer than a disk on a different controller.
vxrelocd moves all subdisks from a failing drive to the same destination disk if possible.
If no spare or free space is found, mail is sent explaining the disposition of volumes that had storage on the failed disk:
dm_name in volume v_name in disk group dg_name. No replacement was made and the disk is still unusable. The following volumes have storage on medianame: volumename ... These volumes are still usable, but the redundancy of those volumes is reduced. Any RAID-5 volumes with storage on the failed disk may become unusable in the face of further failures.Hot-relocation was not successful for subdisks on disk
If any non-RAID-5 volumes were made unusable due to the disk failure, the following message is included:
volumename ... have data on medianame but have no other usable mirrors on other disks. These volumes are now unusable and the data on them is unavailable. These volumes must have their data restored.The following volumes:
If any RAID-5 volumes were made unavailable due to the disk failure, the following message is included:
volumename ... had storage on medianame and have experienced other failures. These RAID-5 volumes are now unusable and data on them is unavailable. These RAID-5 volumes must have their data restored.The following RAID-5 volumes:
If there is spare space available, a snapshot of the current configuration is saved in /etc/vx/saveconfig.d/dg_name.yymmdd_hhmmss.mpvsh before attempting a subdisk relocation. Relocation requires setting up a subdisk on the spare or free space not marked with nohotuse and using it to replace the failed subdisk. If this is successful, the vxrecover command runs in the background to recover the data in volumes that had storage on the disk.
If the relocation fails, the following message is sent:
dm_name in volume v_name in disk group dg_name. No replacement was made and the disk is still unusable.Hot-relocation was not successful for subdiskson disk
If any volumes (RAID-5 or otherwise) become unusable due to the failure, the following message is included:
volumename ... have data on dm_name but have no other usable mirrors on other disks. These volumes are now unusable and the data on them is unavailable. These volumes must have their data restored.The following volumes:
If the relocation procedure was successful and recovery has begun, the following mail message is sent:
v_name Subdisk sd_name relocated to newsd_name, but not yet recovered.Volume
After recovery completes, a mail message is sent relaying the result of the recovery procedure. If the recovery is successful, the following message is included in the mail:
v_name in disk group dg_name.Recovery complete for volume
If the recovery was not successful, the following message is included in the mail:
v_name in disk group dg_name.Failure recovering
from the command line and find the two entries for vxrelocd. Execute the command:
kill -9 PID1 PID2
(substituting PID1 and PID2 with the process IDs for the two vxrelocd processes). To prevent vxrelocd from being started again, you must comment out the line that starts up vxrelocd in the startup script /etc/init.d/vxvm-recover.
Last updated: 28 Jul 2003
Copyright ©2009 Symantec Corporation
All rights reserved.