LVM: mirrored log man page updates
 

Patch name: lvm-mirrored-log-man-page-updates.patch

Man page updates for the new 'mirrored' log type.

Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>

Index: LVM2/man/lvconvert.8.in
================================================== =================
--- LVM2.orig/man/lvconvert.8.in
+++ LVM2/man/lvconvert.8.in
@@ -3,7 +3,7 @@
lvconvert - convert a logical volume from linear to mirror or snapshot
.SH SYNOPSIS
.B lvconvert
--m|--mirrors Mirrors [--mirrorlog {disk|core}] [--corelog] [-R|--regionsize MirrorLogRegionSize]
+-m|--mirrors Mirrors [--mirrorlog {disk|core|mirrored}] [--corelog] [-R|--regionsize MirrorLogRegionSize]
[-A|--alloc AllocationPolicy]
[-b|--background] [-f|--force] [-i|--interval Seconds]
[-h|-?|--help]
@@ -83,6 +83,7 @@ from the data being mirrored.
Core may be useful for short-lived mirrors: It means the mirror is
regenerated by copying the data from the first device again every
time the device is activated - perhaps, for example, after every reboot.
+Using "mirrored" will create a persistent log that is itself mirrored.
.TP
.I --corelog
The optional argument "--corelog" is the same as specifying "--mirrorlog core".
Index: LVM2/man/lvcreate.8.in
================================================== =================
--- LVM2.orig/man/lvcreate.8.in
+++ LVM2/man/lvcreate.8.in
@@ -11,7 +11,7 @@ lvcreate - create a logical volume in a
{-l|--extents LogicalExtentsNumber[%{VG|PVS|FREE}] |
-L|--size LogicalVolumeSize[bBsSkKmMgGtTpPeE]}
[-M|--persistent y|n] [--minor minor]
-[-m|--mirrors Mirrors [--nosync] [--mirrorlog {disk|core}] [--corelog]
+[-m|--mirrors Mirrors [--nosync] [--mirrorlog {disk|core|mirrored}] [--corelog]
[-R|--regionsize MirrorLogRegionSize]]
[-n|--name LogicalVolumeName]
[-p|--permission r|rw] [-r|--readahead ReadAheadSectors|auto|none]
@@ -109,9 +109,10 @@ intensive initial sync of an empty devic
The optional argument --mirrorlog specifies the type of log to be used.
The default is disk, which is persistent and requires
a small amount of storage space, usually on a separate device from the
-data being mirrored. Using core means the mirror is regenerated
+data being mirrored. Using core means the mirror is regenerated
by copying the data from the first device again each time the
-device is activated, for example, after every reboot.
+device is activated, for example, after every reboot. Using "mirrored"
+will create a persistent log that is itself mirrored.

The optional argument --corelog is equivalent to --mirrorlog core.


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel