diff --git a/README b/README index c66c11f11..b65004630 100644 --- a/README +++ b/README @@ -1,13 +1,11 @@ -This directory contains a beta release of LVM2, the new version of -the userland LVM tools designed for the new device-mapper for -the Linux kernel. +This directory contains LVM2, the new version of the userland LVM +tools designed for the new device-mapper for the Linux kernel. The device-mapper needs to be installed before compiling these LVM2 tools. For more information about LVM2 read the WHATS_NEW file. Installation instructions are in INSTALL. -This is beta-quality software, released for testing purposes only. There is no warranty - see COPYING and COPYING.LIB. 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 Mailing list for discussion/bug reports etc. - lvm-devel@sistina.com - Subscribe from http://lists.sistina.com/mailman/listinfo/lvm-devel + linux-lvm@sistina.com + Subscribe from http://lists.sistina.com/mailman/listinfo/linux-lvm diff --git a/VERSION b/VERSION index 47c0d1996..4c899aa45 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -2.00.04-cvs (2003-07-15) +2.00.05-cvs (2003-07-18) diff --git a/WHATS_NEW b/WHATS_NEW index e4cbe9eb6..87392e4b1 100644 --- a/WHATS_NEW +++ b/WHATS_NEW @@ -25,6 +25,7 @@ to provide us with diagnostic information: log { file="/tmp/lvm2.log" level=7 + activation=1 } You should schedule regular backups of your configuration file and diff --git a/man/pvmove.8 b/man/pvmove.8 index 93e78f7fa..700a15c2e 100644 --- a/man/pvmove.8 +++ b/man/pvmove.8 @@ -3,9 +3,10 @@ pvmove \- move physical extents .SH SYNOPSIS .B pvmove +[\-\-abort] [\-d/\-\-debug] [\-h/\-\-help] [\-i/\-\-interval Seconds] [\-v/\-\-verbose] -[\-n/\-\-name LogicalVolume] SourcePhysicalVolume -[DestinationPhysicalVolume[:PE[-PE]...]...] +[\-n/\-\-name LogicalVolume] +[SourcePhysicalVolume [DestinationPhysicalVolume[:PE[-PE]...]...]] .SH DESCRIPTION .B pvmove allows you to move the allocated physical extents (PEs) on @@ -20,15 +21,16 @@ If no .I DestinationPhysicalVolume is specifed, the normal allocation rules for the volume group are used. -If \fBpvmove\fP gets interrupted for any reason, it will probably be -necessary to run \fBvgcfgrestore\fP to restore the volume group's metadata to -the state it was before the \fBpvmove\fP began. - -\fBpvmove\fP locks the volume group and other LVM2 commands can't access -the volume group metadata until \fBpvmove\fP has completed. +If \fBpvmove\fP gets interrupted for any reason (e.g. the machine crashes) +then run \fBpvmove\fP again without any PhysicalVolume arguments to +continue with any moves that were in progress or use \fBpvmove --abort\fP to +abort them. .SH OPTIONS .TP +.I \-\-abort +Abort any moves currently in progress. +.TP .I \-i, \-\-interval Seconds Report progress as a percentage at regular intervals. .TP