Managing Serviceguard 12th Edition, March 2006

Troubleshooting Your Cluster
Replacing Disks
Chapter 8 367
5. On the node from which you issued the lvreduce command, issue
the following command to restore the volume group configuration
data to the newly inserted disk:
# vgcfgrestore -n /dev/vg_sg01 /dev/dsk/c2t3d0
6. Issue the following command to extend the logical volume to the
newly inserted disk:
# lvextend -m 1 /dev/vg_sg01 /dev/dsk/c2t3d0
7. Finally, use the lvsync command for each logical volume that has
extents on the failed physical volume. This synchronizes the extents
of the new disk with the extents of the other mirror.
# lvsync /dev/vg_sg01/lvolname
Replacing a Lock Disk
Replacing a failed lock disk mechanism is the same as replacing a data
disk. If you are using a dedicated lock disk (one with no user data on it),
then you need to issue only one LVM command, as in the following
example:
# vgcfgrestore -n /dev/vg_lock /dev/dsk/c2t3d0
Serviceguard checks the lock disk on an hourly basis. After the
vgcfgrestore command, review the syslog file of an active cluster node
for not more than one hour. Then look for a message showing that the
lock disk is healthy again.
On-line Hardware Maintenance with In-line SCSI
Terminator
In some shared SCSI bus configurations, on-line SCSI disk controller
hardware repairs can be made if HP in-line terminator (ILT) cables are
used. In-line terminator cables are supported with most SCSI-2
Fast-Wide configurations.
In-line terminator cables are supported with Ultra2 SCSI host bus
adapters only when used with the SC10 disk enclosure. This is because
the SC10 operates at slower SCSI bus speeds, which are safe for the use
of ILT cables. In-line terminator cables are not supported for use in any
Ultra160 or Ultra3 SCSI configuration, since the higher SCSI bus speeds
can cause silent data corruption when the ILT cables are used.