From 292358a5172c8688330e4db0f4312ad16b760406 Mon Sep 17 00:00:00 2001 From: Dave Wysochanski Date: Mon, 28 Jun 2010 20:40:15 +0000 Subject: [PATCH] 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 --- doc/example.conf.in | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/example.conf.in b/doc/example.conf.in index 531857128..02c6cd53c 100644 --- a/doc/example.conf.in +++ b/doc/example.conf.in @@ -456,6 +456,17 @@ 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. 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. -- 2.43.5