[lvm-devel] [PATCH 37/38] Update example.conf.in to describe vgmetadatacopies.
Dave Wysochanski
dwysocha at redhat.com
Sat Jun 26 02:53:08 UTC 2010
Update example.conf to note the string value. Special care
must be taken with the string and numeric value - the numbers
must be enclosed in "'s, so this is noted in the comments.
Signed-off-by: Dave Wysochanski <dwysocha at redhat.com>
---
doc/example.conf.in | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/doc/example.conf.in b/doc/example.conf.in
index 5318571..5b1f12f 100644
--- a/doc/example.conf.in
+++ b/doc/example.conf.in
@@ -456,6 +456,19 @@ activation {
# 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. It not an error to set a value larger than
+ # 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 "unmanaged" indicates that LVM should not
+ # automatically manage the 'metadataignore' flags. Note that
+ # this is a string value, so any numbers must be enclosed in '"'s,
+ # for example, vgmetadatacopies = "5".
+
+ # vgmetadatacopies = "unmanaged"
+
# 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.
--
1.6.0.6
More information about the lvm-devel
mailing list