diff options
Diffstat (limited to 'man/pvmove.8.in')
| -rw-r--r-- | man/pvmove.8.in | 106 |
1 files changed, 76 insertions, 30 deletions
diff --git a/man/pvmove.8.in b/man/pvmove.8.in index 83db231..de20abb 100644 --- a/man/pvmove.8.in +++ b/man/pvmove.8.in @@ -3,15 +3,22 @@ pvmove \- move physical extents .SH SYNOPSIS .B pvmove -[\-\-abort] -[\-\-alloc AllocationPolicy] -[\-b|\-\-background] -[\-d|\-\-debug] [\-h|\-\-help] [\-i|\-\-interval Seconds] -[\-\-noudevsync] [\-v|\-\-verbose] [\-n|\-\-name LogicalVolume] -[SourcePhysicalVolume[:PE[-PE]...] [DestinationPhysicalVolume[:PE[-PE]...]...]] +.RB [ \-\-abort ] +.RB [ \-\-alloc +.IR AllocationPolicy ] +.RB [ \-b | \-\-background ] +.RB [ \-d | \-\-debug ] +.RB [ \-h | \-\-help ] +.RB [ \-i | \-\-interval +.IR Seconds ] +.RB [ \-\-noudevsync ] +.RB [ \-v | \-\-verbose ] +.RB [ \-n | \-\-name +.IR LogicalVolume ] +.RI [ SourcePhysicalVolume [ :PE [ -PE ]...] +.RI [ DestinationPhysicalVolume [ :PE [ -PE ]...]...]] .SH DESCRIPTION -.B pvmove -allows you to move the allocated physical extents (PEs) on +pvmove allows you to move the allocated physical extents (PEs) on .I SourcePhysicalVolume to one or more other physical volumes (PVs). You can optionally specify a source @@ -21,25 +28,25 @@ free (or specified) extents on .IR DestinationPhysicalVolume (s). If no .I DestinationPhysicalVolume -is specifed, the normal allocation rules for the volume group are used. +is specified, the normal allocation rules for the Volume Group are used. -If \fBpvmove\fP gets interrupted for any reason (e.g. the machine crashes) -then run \fBpvmove\fP again without any PhysicalVolume arguments to +If pvmove gets interrupted for any reason (e.g. the machine crashes) +then run pvmove again without any PhysicalVolume arguments to restart any moves that were in progress from the last checkpoint. Alternatively use \fBpvmove --abort\fP at any time to abort them at the last checkpoint. You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will ignore -any logical volumes already in the process of being changed, so some +any Logical Volumes already in the process of being changed, so some data might not get moved. \fBpvmove\fP works as follows: -1. A temporary 'pvmove' logical volume is created to store +1. A temporary 'pvmove' Logical Volume is created to store details of all the data movements required. -2. Every logical volume in the volume group is searched +2. Every Logical Volume in the Volume Group is searched for contiguous data that need moving according to the command line arguments. For each piece of data found, a new segment is added to the end of the @@ -49,58 +56,97 @@ from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in the pvmove LV instead of accessing the data directly. -3. The volume group metadata is updated on disk. +3. The Volume Group metadata is updated on disk. -4. The first segment of the pvmove logical volume is activated and starts +4. The first segment of the pvmove Logical Volume is activated and starts to mirror the first part of the data. Only one segment is mirrored at once as this is usually more efficient. 5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it breaks that mirror so that only the new location for that data gets used -and writes a checkpoint into the volume group metadata on disk. +and writes a checkpoint into the Volume Group metadata on disk. Then it activates the mirror for the next segment of the pvmove LV. 6. When there are no more segments left to be mirrored, -the temporary logical volume is removed and the volume group metadata -is updated so that the logical volumes reflect the new data locations. +the temporary Logical Volume is removed and the Volume Group metadata +is updated so that the Logical Volumes reflect the new data locations. Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using \fBvgconvert\fP(8). +N.B. The moving of mirrors, snapshots and their origins is not yet supported. + .SH OPTIONS +See \fBlvm\fP(8) for common options. .TP -.I \-\-abort +.B \-\-abort Abort any moves in progress. .TP -.I \-\-noudevsync +.B \-\-noudevsync Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 creates. .TP -.I \-b, \-\-background +.BR \-b ", " \-\-background Run the daemon in the background. .TP -.I \-i, \-\-interval Seconds +.BR \-i ", " \-\-interval " " \fISeconds Report progress as a percentage at regular intervals. .TP -.I \-n, \-\-name " \fILogicalVolume\fR" +.BR \-n ", " \-\-name " " \fILogicalVolume Move only the extents belonging to .I LogicalVolume from .I SourcePhysicalVolume instead of all allocated extents to the destination physical volume(s). -.SH EXAMPLES -To move all logical extents of any logical volumes on -.B /dev/hda4 -to free physical extents elsewhere in the volume group, giving verbose -runtime information, use: +.SH Examples +To move all Physical Extents that are used by simple Logical Volumes on +/dev/sdb1 to free Physical Extents elsewhere in the Volume Group use: +.sp +.B pvmove /dev/sdb1 +.P +Any mirrors, snapshots and their origins are left unchanged. +.P +Additionally, a specific destination device /dev/sdc1 +can be specified like this: +.sp +.B pvmove /dev/sdb1 /dev/sdc1 +.P +To perform the action only on extents belonging to the single Logical Volume +lvol1 do this: +.sp +.B pvmove -n lvol1 /dev/sdb1 /dev/sdc1 +.P +Rather than moving the contents of the entire device, it is possible to +move a range of Physical Extents - for example numbers 1000 to 1999 +inclusive on /dev/sdb1 - like this: +.sp +.B pvmove /dev/sdb1:1000-1999 +.P +To move a range of Physical Extents to a specific location (which must have +sufficent free extents) use the form: +.sp +.B pvmove /dev/sdb1:1000-1999 /dev/sdc1 +.sp +or +.sp +.B pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999 +.P +If the source and destination are on the same disk, the +.B anywhere +allocation policy would be needed, like this: .sp -\ pvmove -v /dev/hda4 +.B pvmove --alloc anywhere /dev/sdb1:1000-1999 /dev/sdb1:0-999 +.P +The part of a specific Logical Volume present within in a range of Physical +Extents can also be picked out and moved, like this: .sp +.B pvmove -n lvol1 /dev/sdb1:1000-1999 /dev/sdc1 .SH SEE ALSO .BR lvm (8), .BR vgconvert (8) +.BR pvs (8) |