Home > Veritas Storage Foundation™ Volume Manager Manual Pages
/etc/vx/bin/vxreattach -c accessname
This operation may be necessary if a disk has a transient failure, or if Veritas Volume Manager (VxVM) starts with some disk drivers unloaded and unloadable. Disks then enter the failed state. If the problem is fixed, vxreattach may be able to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started.
vxreattach tries to find a disk in the same disk group with the same disk ID for the disk(s) to be reattached. The reattach operation may fail even after finding the disk with the matching disk ID if the original cause (or some other cause) for the disk failure still exists.
vxreattach is usually invoked by vxdiskadm when performing disk recovery. It is not intended to be run directly by an administrator.
See vxintro(1M) for a list of standard exit codes.
/etc/vx/bin/vxreattach -c hdisk14
If reattachment is possible, vxreattach returns with an exit status of 0 and displays the disk group name and disk media name. If reattachment is not possible, vxreattach returns an exit status of 2 and displays an error.
Attempt to reattach the disk in the foreground and try to recover stale plexes of any volumes on the disk:
/etc/vx/bin/vxreattach -r hdisk14
If the reattachment is successful, vxreattach returns an exit status of 0. Otherwise, if an error occurs, vxreattach returns a non-zero exit code as defined on vxintro(1M).
Last updated: 28 Jul 2003
Copyright ©2009 Symantec Corporation
All rights reserved.