All of lore.kernel.org
 help / color / mirror / Atom feed
From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/doc example.conf.in
Date: 28 Jun 2010 20:40:16 -0000	[thread overview]
Message-ID: <20100628204016.21201.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski at sourceware.org	2010-06-28 20:40:16

Modified files:
	doc            : example.conf.in 

Log message:
	Update example.conf.in to describe vgmetadatacopies.
	
	Update example.conf to describe vgmetadatacopies.  Provide an
	explanation for the '0' ("unmanaged") value.
	
	Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.2&r2=1.3

--- LVM2/doc/example.conf.in	2010/05/20 13:47:21	1.2
+++ LVM2/doc/example.conf.in	2010/06/28 20:40:15	1.3
@@ -456,6 +456,17 @@
 
     # pvmetadatacopies = 1
 
+    # Default number of copies of metadata to hold on each VG.
+    # If set to a non-zero value, LVM automatically manages the PV
+    # 'metadataignore' flags (see pvchange) to achieve the requested
+    # copies of metadata.  You may set a value larger than the
+    # the sum of all metadata areas on all physical volumes.  This value
+    # can be overridden on the command line of various commands. The
+    # default value of 0 indicates that LVM should not automatically
+    # manage the 'metadataignore' flags.
+
+    # vgmetadatacopies = 0
+
     # Approximate default size of on-disk metadata areas in sectors.
     # You should increase this if you have large volume groups or
     # you want to retain a large on-disk history of your metadata changes.



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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 20:40 wysochanski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-25 13:06 LVM2/doc example.conf.in snitzer
2010-10-13 15:45 mornfall
2011-04-12 20:44 snitzer
2011-04-26  9:09 prajnoha
2012-03-14 17:13 zkabelac
2012-04-27 18:37 jbrassow
2012-05-10  0:18 agk
2012-05-14 16:29 agk
2012-05-23 12:59 zkabelac

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20100628204016.21201.qmail@sourceware.org \
    --to=wysochanski@sourceware.org \
    --cc=lvm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.