pvmove.1m (2010 09)

p
pvmove(1M) pvmove(1M)
source_pv_path physical volume will be returned to a "stand-by" spare physical volume. This is how to
"unspare" data once the original failed physical volume has been repaired and is available to receive data.
Auto-Rebalance Mode
For volume group 2.0 and higher, the
pvmove command provides an -a option for performing automatic
re-balance of allocated extents for space. In automatic re-balance mode, the relocation of extents is based
on the optimal number of extents calculated for each logical volume on each physical volume involved in
the automatic re-balance operation.
The optimal number of extents calculated will keep the percentage of free and used space on each
involved physical volume equal to the total percentage of free and used space on all the physical volume’s
that are selected in the automatic re-balance operation.
When invoked in the automatic re-balance mode, the
pvmove command will try to achieve the optimal
count of extents on each physical volume involved in the operation. If the current configuration of the
volume group do not allow this, it still proceeds with the distribution of extents staying as close as possi-
ble to the optimal count.
Either the whole volume group or one or more logical volumes can be automatically re-balanced across all
physical volumes of the volume group using the
-a option with the pvmove command.
A single or multiple logical volumes can be automatically re-balanced across either one or more physical
volumes or all physical volumes belonging to the volume group.
Note that when a single or multiple logical volumes are provided, then the automatic re-balance opera-
tion will not move extents belonging to other logical volumes in order to balance the extents belonging to
the specified logical volumes.
The
-f option in conjunction with -a option can be used to move all the used extents from a single or
multiple physical volumes to the remaining physical volumes in the volume group such that the remain-
ing physical volumes are balanced with respect to space utilization.
The following syntax is used to perform automatic re-balance of allocated extents for space within a
volume group:
/usr/sbin/pvmove [
-A autobackup ][-p [-s]] -a vg_name
The following syntax is used to perform an automatic re-balance of allocated extents for space belonging
to one or more logical volumes either within a volume group or across one or more physical volumes, or
one or more physical volume groups (PVG):
/usr/sbin/pvmove [
-A autobackup ][-p [-s]] -a lv_path ... [pv_path ... | dest_pvg_name...]
This last syntax is used to free up one or more physical volumes in a volume group by keeping the
remaining volume group space balanced:
/usr/sbin/pvmove [
-A autobackup ][-p [-s]] -a -f pv_path ...
Bootable PV Considerations
The
pvmove command supports moving boot physical volumes, and the resulting (destination) physical
volumes are bootable.
However, please note that when auto-rebalance (
pvmove -a) is run on bootable physical volumes, the
logical volumes for root, boot, swap, and dump are not moved/rebalanced; therefore it ensures that the
system is still bootable after a rebalance.
Shared Volume Group Considerations
For volume group version 1.0
pvmove is not supported if the volume group is activated in shared mode.
For volume groups version 2.0 and higher, pvmove can be performed on volume groups activated in
either shared or unshared mode.
The
lvmpud daemon must be running on all the nodes sharing a volume group actived in shared mode.
See lvmpud (1M).
LMV shared mode is currently only available in Serviceguard clusters.
Snapshot Volume Considerations
Note that for volume group version 2.2 or higher, pvmove is disallowed in share mode if it has snapshots
associated with it.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010