Version 2.02.34 -
===================================
- Update vgsplit to take "-n LogicalVolumeName" on the commandline.
+ Update vgsplit man page to reflect lvnames on the cmdline.
+ Update vgsplit to take "-n LogicalVolumeName" on the cmdline.
Use clustered mirror log with pvmove in clustered VGs, if available.
Fix some pvmove error status codes.
Fix vgsplit error paths to release vg_to lock.
.IR type ]
.RB [ -p | \-\-maxphysicalvolumes
.IR MaxPhysicalVolumes ]
+.RB [ \-n | \-\-name
+.IR LogicalVolumeName ]
.RB [ \-t | \-\-test ]
.RB [ \-v | \-\-verbose ]
SourceVolumeGroupName DestinationVolumeGroupName
-PhysicalVolumePath [PhysicalVolumePath...]
+[ PhysicalVolumePath ...]
.SH DESCRIPTION
.B vgsplit
-moves
-.IR PhysicalVolumePath (s)
-from
+moves one or more physical volumes from
.I SourceVolumeGroupName
into
-.I DestinationVolumeGroupName\fP.
+.I DestinationVolumeGroupName\fP. The physical volumes moved can be
+specified either explicitly via \fIPhysicalVolumePath\fP, or implicitly by
+\fB-n\fP \fILogicalVolumeName\fP, in which case only physical volumes
+underlying the specified logical volume will be moved.
If
.I DestinationVolumeGroupName
volume group attributes with an existing destination volume group is an error,
and no split will occur.
-Logical Volumes cannot be split between Volume Groups.
-Each existing Logical Volume must be entirely on the Physical Volumes forming
-either the source or the destination Volume Group.
+Logical volumes cannot be split between volume groups. \fBVgsplit(8)\fP only
+moves complete physical volumes: To move part of a physical volume, use
+\fBpvmove(8)\fP. Each existing logical volume must be entirely on the physical
+volumes forming either the source or the destination volume group. For this
+reason, \fBvgsplit(8)\fP may fail with an error if a split would result in a
+logical volume being split across volume groups.
+
.SH OPTIONS
See \fBlvm\fP for common options.
.SH SEE ALSO