Disk repair is a mirrored disk operation that copies data from the good drive to the bad drive to bring a mirrored pair to a consistent state without interrupting applications accessing the volume set. After the repair operation is completed, normal mirroring resumes.
The system starts repairing a disk when one of the following occurs:
Operator starts repair | Operator issues the REPLACEMIRRVOL command to start repair.
|
System automatically starts repair | Upon volume mount, the system checks to make sure both partner disks contain the same information. If partner disks do not contain the same information, the good disk and the bad disk are identified and the repair begins.
|
All mirrored pairs on the system cannot be repaired at once. There is a limit of six repair operations taking place at the same time. This is to limit the performance impact of repairing on the system. The repairs are staged, such that when one of the six repairs finishes, another begins.
 |
 |  |
 |
 | NOTE: If a system crash occurs and the system is restarted, the mirrored disk system always performs a disk repair on all of the mirrored disk partners. The repairs are staged. |
 |
 |  |
 |
Drives that are staged (awaiting repair) transition to the repair state in order of mounting. If the maximum number of repairs is taking place, subsequent pairs that mount and get staged are serviced in the order that they are mounted.
 |
 |  |
 |
 | NOTE: Any disk pair that has one partner go DISABLED, (and has a REPLACEMIRRVOL command issued), always begins an immediate repair and is not staged. |
 |
 |  |
 |
You can use the VOLUTIL SHOWSET command to display volumes involved in the repair process.
:VOLUTIL
Mirvutil A.00.00, (C) Hewlett-Packard Co., 1990.
All Rights Reserved.
volutil:SHOWSET PROD_SET MIRROR
Volume Name Vol Status Mirr Status Ldev Mirr ldev
- - - - - - - - - - - - - - - - - - - - - - - - - -
MEMBER1 MASTER NORMAL 30 31
MEMBER1 MASTER NORMAL 31 30
MEMBER2 MEMBER REPAIR-DEST 32 33
MEMBER2 MEMBER REPAIR-SRCE 33 32
|
The above screen shows that LDEV 32 (REPAIR-DEST) is being repaired by LDEV 33 (REPAIR-SRCE). The repair process takes about twenty minutes to complete. The
time is an only an estimate and can take up to an hour and a half. Programs and data residing on MEMBER2 are available while repairs are taking place.