Creating A Spare Disk - HP -UX 11i Administrator's Manual

Example
Consider a volume group having the configuration below:
Three physical volumes each of size 1245 extents:
/dev/disk/disk10, /dev/disk/disk11, and /dev/disk/disk12.
Three logical volumes all residing on same disk, /dev/disk/disk10:
/dev/vg_01/lvol1 (Size = 200 extents),
/dev/vg_01/lvol2 (Size = 300 extents),
/dev/vg_01/lvol3 (Size = 700 extents).
The pvmove below generates a summary report to preview the re-balance of volume group vg_01:
# pvmove -p -s -a vg_01
--- Summary Report of re-balance operation ---
The optimal percentage of free space per PV = 68%
The optimal percentage of used space per PV = 32%
--- Before re-balance operation ---
The average percentage of free space on each PV =~ (68 +/- 32)%
The average percentage of used space on each PV =~ (32 +/- 32)%
--- After re-balance operation ---
The average percentage of free space on each PV =~ (68 +/- 0)%
The average percentage of used space on each PV =~ (32 +/- 0)%
The output above is interpreted as follows:
The average percentage free space on each PV, before re-balance operation, is approximately
in the range of (68 - 32 =) 36% to (68 + 32 = ) 100% and after re-balance operation would
be approximately (68 +/- 0 =) 68%.
The average percentage used space on each PV, before re-balance operation, is approximately
in the range of (32 - 32 = ) 0% to (32 + 32 =) 64% and after re-balance operation would be
approximately (32 +/- 0 =) 32%.
The pvmove command below actually moves the data for balancing:
# pvmove -a vg_01
Automatic re-balance operation successfully completed.
Volume Group configuration for /dev/vg_01 has been saved in
/etc/lvmconf/vg_01.conf
NOTE: In the automatic re-balance mode, the pvmove command tries to achieve an optimal
rebalance, but it does not guarantee an optimal rebalance; and there are scenarios where the
user can perform a more optimal rebalance manually than the one provided by the pvmove auto
rebalance operation.
The auto re-balance operation does not move/re-balance boot, root, swap, or dump physical
volumes, so resulting system is still bootable.
The auto re-balance will fail if the operation involves moving pre-allocated extents belonging to a
snapshot. For information about pre-allocated extents of snapshots, see
Snapshot Logical Volumes" (page

Creating a Spare Disk

NOTE: Disk sparing requires the optional product HP MirrorDisk/UX.
Version 2.x volume groups do not support disk sparing.
To configure a spare physical volume into a volume group for which you want protection against
disk failure, follow these steps before a disk failure actually occurs:
76 Administering LVM
103).
"Creating and Administering