public inbox for
help / color / mirror / Atom feed
Subject: LVM2/man
Date: Mon, 28 Jun 2010 20:36:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	2010-06-28 20:36:18

Modified files:
	man            : 

Log message:
	Define vgmetadatacopies in vgchange man page.
	This patch adds a vgmetadatacopies parameter for metadata balancing.
	This parameter provides a simple way for users to create a policy for
	placing metadata on PVs automatically by LVM.  The behavior is implemented
	inside LVM by managing the 'ignore' mda bits.  We chose the name
	'vgmetadatacopies' as this is a natural extension to the existing parameter
	'pvmetadatacopies' / 'metadatacopies' in pvcreate.
	This is a first step at VG parameter based metadata balancing.  Most users
	will probably want to state that they want a certain number of PVs to contain
	metadata, and they may be less concerned about a specific number of metadata
	copies in the volume group.  However, for default values (pvmetadatacopies
	is 1 by default), the number of metadatacopies in the volume group, and the
	number of PVs with metadata are the same.  In the future we could add
	vgmetadatacopiespvs to define more specifically the number of pvs in the
	VG that contain metadata, but for now we start with this parameter.
	Another possible future extension would be to define a specific pv tag
	to mark the set of PVs that should be used for metadata balancing.  This
	tag based approach could be used in conjunction with 'vgmetadatacopies'.
	Signed-off-by: Dave Wysochanski <>


--- LVM2/man/	2010/05/06 11:15:55	1.9
+++ LVM2/man/	2010/06/28 20:36:18	1.10
@@ -25,6 +25,8 @@
 .IR MaxLogicalVolumes ]
 .RB [ -p | \-\-maxphysicalvolumes
 .IR MaxPhysicalVolumes ]
+.RB [ \-\-[vg]metadatacopies ]
+.IR NumberOfCopies|unmanaged|all ]
 .RB [ \-P | \-\-partial]
 .RB [ \-s | \-\-physicalextentsize
 .IR PhysicalExtentSize [ \fBbBsSkKmMgGtTpPeE\fR ]]
@@ -127,13 +129,23 @@
 Changes the maximum number of physical volumes that can belong
 to this volume group.
 For volume groups with metadata in lvm1 format, the limit is 255.
-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.
+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.
+.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.
 .BR \-s ", " \-\-physicalextentsize " " \fIPhysicalExtentSize\fR[\fBbBsSkKmMgGtTpPeE\fR]
 Changes the physical extent size on physical volumes of this volume group.

                 reply	other threads:[~2010-06-28 20:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).