
In this example, LUN instance 28 was created for the new disk, with LUN hardware path
64000/0xfa00/0x1c, device special files /dev/disk/disk28 and /dev/rdisk/disk28, at
the same lunpath hardware path as the old disk, 0/1/1/1.0x3.0x0. The old LUN instance 14
for the old disk now has no lunpath associated with it.
Note: If the system was rebooted to replace the failed disk, ioscan –m lun does not display
the old disk.
5. Assign the old instance number to the replacement disk. For example:
# io_redirect_dsf -d /dev/disk/disk14 -n /dev/disk/disk28
This assigns the old LUN instance number (14) to the replacement disk. In addition, the device
special files for the new disk are renamed to be consistent with the old LUN instance number.
The following ioscan –m lun output shows the result:
# ioscan –m lun /dev/disk/disk14
Class I Lun H/W Path Driver S/W State H/W Type Health Description
========================================================================
disk 14 64000/0xfa00/0x1c esdisk CLAIMED DEVICE online HP MSA Vol
0/1/1/1.0x3.0x0
/dev/disk/disk14 /dev/rdisk/disk14
The LUN representation of the old disk with LUN hardware path 64000/0xfa00/0x0 was
removed. The LUN representation of the new disk with LUN hardware path
64000/0xfa00/0x1c was reassigned from LUN instance 28 to LUN instance 14 and its device
special files were renamed as /dev/disk/disk14 and /dev/rdisk/disk14.
6. Restore LVM configuration information to the new disk. For example:
# vgcfgrestore -n /dev/vgnn /dev/rdisk/disk14
7. Restore LVM access to the disk.
If you did not reboot the system in step 2, reattach the disk as follows:
# pvchange –a y /dev/disk/disk14
If you did reboot the system, reattach the disk by reactivating the volume group as follows:
# vgchange -a y /dev/vgnn
NOTE: You can run the vgchange command with the -a y option on a volume group that is
deactivated or already activated. It attaches all paths for all disks in the volume group and
resumes automatically recovering any disks in the volume group that were offline or any disks in
the volume group that were replaced. Therefore, run vgchange only after all work has been
completed on all disks and paths in the volume group, and it is necessary to attach them all.
8. Recover any lost data.
LVM recovers all the mirrored logical volumes on the disk, and starts that recovery when the
volume group is activated.
For all the unmirrored logical volumes that you identified in step 2, restore the data from backup
and re-enable user access as follows:
Comentarios a estos manuales