shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2025-03-10 16:58:47 +03:00
Code Releases Activity

update

Browse Source
This commit is contained in:
Alasdair Kergon 2003-07-18 00:41:04 +00:00
parent 21a1fa4701
commit 5518374bd9
4 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README
View File

@ -1,13 +1,11 @@
This directory contains a beta release of LVM2, the new version of This directory contains LVM2, the new version of the userland LVM
the userland LVM tools designed for the new device-mapper for tools designed for the new device-mapper for the Linux kernel.
the Linux kernel.
The device-mapper needs to be installed before compiling these LVM2 tools. The device-mapper needs to be installed before compiling these LVM2 tools.
For more information about LVM2 read the WHATS_NEW file. For more information about LVM2 read the WHATS_NEW file.
Installation instructions are in INSTALL. Installation instructions are in INSTALL.
This is beta-quality software, released for testing purposes only.
There is no warranty - see COPYING and COPYING.LIB. There is no warranty - see COPYING and COPYING.LIB.
Tarballs are available from: Tarballs are available from:
@ -20,6 +18,6 @@ To access the CVS tree use:
cvs -d :pserver:cvs@tech.sistina.com:/data/cvs checkout LVM2 cvs -d :pserver:cvs@tech.sistina.com:/data/cvs checkout LVM2
Mailing list for discussion/bug reports etc. Mailing list for discussion/bug reports etc.
lvm-devel@sistina.com linux-lvm@sistina.com
Subscribe from http://lists.sistina.com/mailman/listinfo/lvm-devel Subscribe from http://lists.sistina.com/mailman/listinfo/linux-lvm

2
VERSION
View File

@ -1 +1 @@
2.00.04-cvs (2003-07-15) 2.00.05-cvs (2003-07-18)

1
WHATS_NEW
View File

@ -25,6 +25,7 @@ to provide us with diagnostic information:
log { log {
file="/tmp/lvm2.log" file="/tmp/lvm2.log"
level=7 level=7
activation=1
} }
You should schedule regular backups of your configuration file and You should schedule regular backups of your configuration file and

18
man/pvmove.8
View File

@ -3,9 +3,10 @@
pvmove \- move physical extents pvmove \- move physical extents
.SH SYNOPSIS .SH SYNOPSIS
.B pvmove .B pvmove
[\-\-abort]
[\-d/\-\-debug] [\-h/\-\-help] [\-i/\-\-interval Seconds] [\-v/\-\-verbose] [\-d/\-\-debug] [\-h/\-\-help] [\-i/\-\-interval Seconds] [\-v/\-\-verbose]
[\-n/\-\-name LogicalVolume] SourcePhysicalVolume [\-n/\-\-name LogicalVolume]
[DestinationPhysicalVolume[:PE[-PE]...]...] [SourcePhysicalVolume [DestinationPhysicalVolume[:PE[-PE]...]...]]
.SH DESCRIPTION .SH DESCRIPTION
.B pvmove .B pvmove
allows you to move the allocated physical extents (PEs) on allows you to move the allocated physical extents (PEs) on
@ -20,15 +21,16 @@ If no
.I DestinationPhysicalVolume .I DestinationPhysicalVolume
is specifed, the normal allocation rules for the volume group are used. is specifed, the normal allocation rules for the volume group are used.
If \fBpvmove\fP gets interrupted for any reason, it will probably be If \fBpvmove\fP gets interrupted for any reason (e.g. the machine crashes)
necessary to run \fBvgcfgrestore\fP to restore the volume group's metadata to then run \fBpvmove\fP again without any PhysicalVolume arguments to
the state it was before the \fBpvmove\fP began. continue with any moves that were in progress or use \fBpvmove --abort\fP to
abort them.
\fBpvmove\fP locks the volume group and other LVM2 commands can't access
the volume group metadata until \fBpvmove\fP has completed.
.SH OPTIONS .SH OPTIONS
.TP .TP
.I \-\-abort
Abort any moves currently in progress.
.TP
.I \-i, \-\-interval Seconds .I \-i, \-\-interval Seconds
Report progress as a percentage at regular intervals. Report progress as a percentage at regular intervals.
.TP .TP