15
18
.RB [ \-v | \-\-verbose ]
16
19
.RB [ \-n | \-\-name
17
20
.IR LogicalVolume ]
18
.RI [ SourcePhysicalVolume [ :PE [ -PE ]...]
19
.RI [ DestinationPhysicalVolume [ :PE [ -PE ]...]...]]
21
.RI [ SourcePhysicalVolume [ :PE [ \-PE ]...]
22
.RI [ DestinationPhysicalVolume [ :PE [ \-PE ]...]...]]
21
24
pvmove allows you to move the allocated physical extents (PEs) on
22
25
.I SourcePhysicalVolume
33
36
If pvmove gets interrupted for any reason (e.g. the machine crashes)
34
37
then run pvmove again without any PhysicalVolume arguments to
35
38
restart any moves that were in progress from the last checkpoint.
36
Alternatively use \fBpvmove --abort\fP at any time to abort them
37
at the last checkpoint.
39
Alternatively use \fBpvmove \-\-abort\fP at any time to abort. The
40
resulting location of logical volumes after an abort is issued depends
43
option was used when starting the pvmove process.
39
45
You can run more than one pvmove at once provided they are moving data
40
46
off different SourcePhysicalVolumes, but additional pvmoves will ignore
75
81
Note that this new process cannot support the original LVM1
76
82
type of on-disk metadata. Metadata can be converted using \fBvgconvert\fP(8).
86
option is used, a slightly different approach is used for the move. Again,
87
a temporary 'pvmove' logical volume is created to store the details of all
88
the data movements required. This temporary LV contains all the segments of
89
the various LVs that need to be moved. However this time, an identical
90
logical volume is allocated that contains the same number of segments and
91
a mirror is created to copy the contents from the first temporary LV to the
92
second. When a complete copy is accomplished, the temporary logical volumes
93
are removed, leaving behind the segments on the destination physical volume.
94
If an abort is issued during the move, all logical volumes being moved will
95
remain on the source physical volume.
79
98
See \fBlvm\fP(8) for common options.
82
Abort any moves in progress.
101
Abort any moves in progress. If the
103
option was used to start the pvmove, all logical volumes will remain on
104
the source physical volume. Otherwise, those segments that have completed
105
the move will stay on the destination physical volume, while those that
106
have not will remain on the source physical volume.
109
Make the entire operation atomic. That is, ensure that all affected logical
110
volumes are moved to the destination physical volume together; unless the move
111
has been aborted. If the move has been aborted, all logical volumes will
112
remain on the source physical volume.
85
115
Disable udev synchronisation. The
115
145
To perform the action only on extents belonging to the single Logical Volume
118
.B pvmove -n lvol1 /dev/sdb1 /dev/sdc1
148
.B pvmove \-n lvol1 /dev/sdb1 /dev/sdc1
120
150
Rather than moving the contents of the entire device, it is possible to
121
151
move a range of Physical Extents - for example numbers 1000 to 1999
122
152
inclusive on /dev/sdb1 - like this:
124
.B pvmove /dev/sdb1:1000-1999
154
.B pvmove /dev/sdb1:1000\-1999
126
156
A range can also be specified as start+length, so
133
163
To move a range of Physical Extents to a specific location (which must have
134
164
sufficient free extents) use the form:
136
.B pvmove /dev/sdb1:1000-1999 /dev/sdc1
166
.B pvmove /dev/sdb1:1000\-1999 /dev/sdc1
140
.B pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999
170
.B pvmove /dev/sdb1:1000\-1999 /dev/sdc1:0\-999
142
172
If the source and destination are on the same disk, the
144
174
allocation policy would be needed, like this:
146
.B pvmove --alloc anywhere /dev/sdb1:1000-1999 /dev/sdb1:0-999
176
.B pvmove \-\-alloc anywhere /dev/sdb1:1000\-1999 /dev/sdb1:0\-999
148
178
The part of a specific Logical Volume present within in a range of Physical
149
179
Extents can also be picked out and moved, like this:
151
.B pvmove -n lvol1 /dev/sdb1:1000-1999 /dev/sdc1
181
.B pvmove \-n lvol1 /dev/sdb1:1000\-1999 /dev/sdc1
154
184
.BR vgconvert (8)
added
removed
man/pvmove.8.in
