mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
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>
This commit is contained in:
parent
a9d8bf269a
commit
292358a517
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user