Hot-spare disk policies

You can designate disks as hot-spare disks for a volume group with mirrored logical volumes.

When you designate which disks to use as hot-spare disks, you can specify a policy to be used if a disk or disks start to fail and you can specify synchronization characteristics.

If you add a physical volume to a volume group (to mark it as a hot-spare disk), the disk must have at least the same capacity as the smallest disk already in the volume group. When this feature is implemented, data will be migrated to a hot-spare disk when Mirror Write Consistency (MWC) write failures mark a physical volume missing.

chvg -hhotsparepolicy -ssyncpolicy VolumeGroup

Where hotsparepolicy determines which of the following policies you want to use when a disk is failing:

y

Automatically migrates partitions from one failing disk to one spare disk. From the pool of hot spare disks, the smallest one that is big enough to substitute for the failing disk will be used.

Y

Automatically migrates partitions from a failing disk, but might use the complete pool of hot-spare disks.

n

Does not migrate automatically (default).

r

Removes all disks from the pool of hot-spare disks for this volume group.

The syncpolicy argument determines whether you want to synchronize any stale partitions automatically:

y

Automatically tries to synchronize stale partitions.

n

Does not automatically try to synchronize stale partitions. (This option is the default.)

The VolumeGroup argument specifies the name of the associated mirrored volume group.