1
0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00

Fix default value of metadatacopies in documentation (2->1).

This commit is contained in:
Alasdair Kergon 2005-03-03 21:52:58 +00:00
parent eb3037ddbd
commit f3b0ea286a
3 changed files with 6 additions and 6 deletions

View File

@ -1,5 +1,6 @@
Version 2.01.06 -
====================================
Fix default value of metadatacopies in documentation (2->1).
Fix clvmd-gulm locking.
./configure --enable-debug now enables debugging code in clvmd.
Fix clvmd-gulm node up/down code so it actually works.

View File

@ -258,11 +258,10 @@ activation {
#
# metadata {
# Default number of copies of metadata to hold on each PV. 0, 1 or 2.
# It's best to leave this at 2.
# You might want to override it from the command line with 0 or 1
# You might want to override it from the command line with 0
# when running pvcreate on new PVs which are to be added to large VGs.
# pvmetadatacopies = 2
# pvmetadatacopies = 1
# Approximate default size of on-disk metadata areas in sectors.
# You should increase this if you have large volume groups or

View File

@ -91,10 +91,10 @@ The approximate amount of space to be set aside for each metadata area.
.BR \-\-metadatacopies " copies"
The number of metadata areas to set aside on each PV. Currently
this can be 0, 1 or 2.
If set to 2 (the default), two copies of the volume group metadata
If set to 2, two copies of the volume group metadata
are held on the PV, one at the front of the PV and one at the end.
If set to 1, one copy is kept at the front of the PV (starting in the
5th sector).
If set to 1 (the default), one copy is kept at the front of the PV
(starting in the 5th sector).
If set to 0, no copies are kept on this PV - you might wish to use this
with VGs containing large numbers of PVs. But if you do this and
then later use \fBvgsplit\fP you must ensure that each VG is still going