diff options
author | Dave Wysochanski <dwysocha@redhat.com> | 2010-06-28 20:38:23 +0000 |
---|---|---|
committer | Dave Wysochanski <dwysocha@redhat.com> | 2010-06-28 20:38:23 +0000 |
commit | 9e111ef67a5ccd5b88c4f20077747a57fba09eba (patch) | |
tree | 3690000b2f51a75811e504ce718ed09ddd892029 /man | |
parent | 60a5f61fc85e8a88fab556f9eb0aca44ea3398b1 (diff) | |
download | lvm2-9e111ef67a5ccd5b88c4f20077747a57fba09eba.tar.gz lvm2-9e111ef67a5ccd5b88c4f20077747a57fba09eba.tar.xz lvm2-9e111ef67a5ccd5b88c4f20077747a57fba09eba.zip |
Add --vgmetadatacopies to vgcreate man page, command, and lvm.conf.
Allow parsing of --vgmetadatacopies for vgcreate. Accept
--metadatacopies as a synonym for --vgmetadatacopies.
Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
Diffstat (limited to 'man')
-rw-r--r-- | man/lvm.conf.5.in | 22 | ||||
-rw-r--r-- | man/vgcreate.8.in | 27 |
2 files changed, 41 insertions, 8 deletions
diff --git a/man/lvm.conf.5.in b/man/lvm.conf.5.in index 02ebb2a0..88f3ab35 100644 --- a/man/lvm.conf.5.in +++ b/man/lvm.conf.5.in @@ -386,7 +386,7 @@ to store on each physical volume. Currently it can be set to 0, 1 or 2. The default is 1. If set to 2, one copy is placed at the beginning of the disk and the other is placed at the end. -It can be overridden on the command line with \fB--metadatacopies\fP. +It can be overridden on the command line with \fB--pvmetadatacopies\fP. If creating a volume group with just one physical volume, it's a good idea to have 2 copies. If creating a large volume group with many physical volumes, you may decide that 3 copies of the metadata @@ -406,6 +406,26 @@ The metadata areas are treated as circular buffers, so unused space becomes filled with an archive of the most recent previous versions of the metadata. .IP +\fBvgmetadatacopies\fP \(em When creating a volume group using the +LVM2 metadata format, this is the default number of copies of metadata +desired across all the physical volumes in the volume group. If set to +a non-zero value, LVM will automatically set or clear the metadataignore +flag on the physical volumes (see \fBpvchange --metadataignore\fP) in order +to achieve the desired number of metadata copies. An LVM command that +adds or removes physical volumes (for example, \fBvgextend\fP, \fBvgreduce\fP, +\fBvgsplit\fP, or \fBvgmerge\fP), may cause LVM to automatically set or +clear the metadataignore flags. Also, if physical volumes go missing or +reappear, or a new number of copies is explicitly set (see +\fBvgchange --vgmetadatacopies\fP), LVM may adjust the metadataignore flags. +Set \fBvgmetadatacopies\fP to 0 instructs LVM not to set or clear the +metadataignore flags automatically. You may set a value larger than the +sum of all metadata areas on all physical volumes. The value can +be overridden on the command line with \fB--vgmetadatacopies\fP for various +commands (for example, \fBvgcreate\fP and \fBvgchange\fP), and can be +queryied with the \fBvg_mda_copies\fP field of \fBvgs\fP. This option +is useful for volume groups containing large numbers of physical volumes +with metadata as it may be used to minimize metadata read and write overhead. +.IP \fBdirs\fP \(em List of directories holding live copies of LVM2 metadata as text files. These directories must not be on logical volumes. It is possible to use LVM2 with a couple of directories diff --git a/man/vgcreate.8.in b/man/vgcreate.8.in index 06e00069..e3d970e3 100644 --- a/man/vgcreate.8.in +++ b/man/vgcreate.8.in @@ -16,6 +16,8 @@ vgcreate \- create a volume group .RB [ -M | \-\-metadatatype type] .RB [ -p | \-\-maxphysicalvolumes .IR MaxPhysicalVolumes ] +.RB [ \-\-[vg]metadatacopies ] +.IR NumberOfCopies|unmanaged|all ] .RB [ \-s | \-\-physicalextentsize .IR PhysicalExtentSize [ \fBbBsSkKmMgGtTpPeE\fR ]] .RB [ \-t | \-\-test ] @@ -66,13 +68,24 @@ to this volume group. The setting can be changed with \fBvgchange\fP. For volume groups with metadata in lvm1 format, the limit and default value is 255. -If the metadata uses lvm2 format, the default value is 0 -which removes this restriction: there is then no limit. -If you have a large number of physical volumes in -a volume group with metadata in lvm2 format, -for tool performance reasons, you should consider -some use of \fB--pvmetadatacopies 0\fP -as described in \fBpvcreate(8)\fP. +If the metadata uses lvm2 format, the value 0 removes this restriction: +there is then no limit. If you have a large number of physical volumes in +a volume group with metadata in lvm2 format, for tool performance reasons, +you should consider some use of \fB--pvmetadatacopies 0\fP as described in +\fBpvcreate(8)\fP, and/or use \fB--vgmetadatacopies\fP. +.TP +.BR \-\-vgmetadatacopies " " \fINumberOfCopies|unmanaged|all\fP +Sets the desired number of metadata copies in the volume group. If set to +a non-zero value, LVM will automatically manage the 'metadataignore' +flags on the physical volumes (see \fBpvchange --metadataignore\fP) in order +to achieve \fINumberOfCopies\fP copies of metadata. If set to \fIunmanaged\fP, +LVM will not automatically manage the 'metadataignore' flags. If set to +\fIall\fP, LVM will first clear all of the 'metadataignore' flags on all +metadata areas in the volume group, then set the value to \fIunmanaged\fP. +The \fBvgmetadatacopies\fP option is useful for volume groups containing +large numbers of physical volumes with metadata as it may be used to +minimize metadata read and write overhead. +The default value is \fIunmanaged\fP. .TP .BR \-s ", " \-\-physicalextentsize " " \fIPhysicalExtentSize\fR[\fBbBsSkKmMgGtTpPeE\fR] Sets the physical extent size on physical volumes of this volume group. |