# scsimgr replace_wwid –D /dev/rdisk/disk14
This command lets the storage subsystem replace the old disk’s LUN World-Wide-Identifier
(WWID) with the new disk’s LUN WWID. The storage subsystem creates a new LUN instance and
new device special files for the replacement disk.
5. Determine the new LUN instance number for the replacement disk. For example:
# ioscan –m lun
Class I Lun H/W Path Driver S/W State H/W Type Health Description
========================================================================
disk 14 64000/0xfa00/0x0 esdisk NO_HW DEVICE offline HP MSA Vol
/dev/disk/disk14 /dev/rdisk/disk14
...
disk 28 64000/0xfa00/0x1c esdisk CLAIMED DEVICE online HP MSA Vol
0/1/1/1.0x3.0x0
/dev/disk/disk28 /dev/rdisk/disk28
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, running ioscan –m lun does not
display the old disk.
6. 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.
7. Restore LVM configuration information to the disk. For example:
# vgcfgrestore -n /dev/vgnn /dev/rdisk/disk14
8. 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:
Komentarze do niniejszej Instrukcji