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

Minor changes to man pages for --metadataignore.

Browse Source 
Move the definition from pvchange to pvcreate - the location of
other metadata options.
This commit is contained in:
Dave Wysochanski 2010-07-02 17:05:22 +00:00
parent d0709eed62
commit 1c0c6cc812
5 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
man/lvm.conf.5.in
View File

@ -415,7 +415,7 @@ line with \fB--metadataignore\fP. Metadata areas cannot be created
or extended after Logical Volumes have been allocated on the device.
If you do not want to store metadata on this device, it is still wise
always to allocate a metadata area (use a non-zero value for
\fB--pvmetadatacopies) in case you need it in the future and to use
\fB--pvmetadatacopies\fP) in case you need it in the future and to use
this option to instruct LVM2 to ignore it.
.IP
\fBvgmetadatacopies\fP \(em When creating a volume group using the

10
man/pvchange.8.in
View File

@ -26,16 +26,6 @@ Generate new random UUID for specified physical volumes.
.TP
.I \-x, \-\-allocatable y|n
Enable or disable allocation of physical extents on this physical volume.
.TP
.I \-\-metadataignore y|n
Ignore or un-ignore metadata areas on this physical volume. If metadata
areas on a physical volume are ignored, LVM will not not store metadata
in the metadata areas present on this Physical Volume. Metadata areas
cannot be created or extended after Logical Volumes have been allocated
on the device. If you do not want to store metadata on this device, it
is still wise always to allocate a metadata area in case you need it in
the future and to use this option to instruct LVM2 to ignore it.
(This option is not applicable to the old LVM1 metadata format.)
.SH Example
"pvchange -x n /dev/sdk1" disallows the allocation of physical extents
on this physical volume (possibly because of disk errors, or because it will

10
man/pvcreate.8.in
View File

@ -118,6 +118,16 @@ 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
to have a suitable number of copies of the metadata after the split!
.TP
.I \-\-metadataignore y|n
Ignore or un-ignore metadata areas on this physical volume. The default
is "n". If metadata areas on a physical volume are ignored, LVM will
not not store metadata in the metadata areas present on this Physical
Volume. Metadata areas cannot be created or extended after Logical
Volumes have been allocated on the device. If you do not want to store
metadata on this device, it is still wise always to allocate a metadata
area in case you need it in the future and to use this option to instruct
LVM2 to ignore it.
.TP
.BR \-\-restorefile " file"
In conjunction with \fB--uuid\fP, this extracts the location and size
of the data on the PV from the file (produced by \fBvgcfgbackup\fP)

2
man/vgchange.8.in
View File

@ -138,7 +138,7 @@ you should consider some use of \fB--pvmetadatacopies 0\fP as described in
.BR \-\-vgmetadatacopies " " \fINumberOfCopies|unmanaged|all\fP
Sets the desired number of metadata copies in the volume group. If set to
a non-zero value, LVM will automatically manage the 'metadataignore'
flags on the physical volumes (see \fBpvchange --metadataignore\fP) in order
flags on the physical volumes (see \fBpvchange\fP or \fBpvcreate\fP --metadataignore\fP) in order
to achieve \fINumberOfCopies\fP copies of metadata. If set to \fIunmanaged\fP,
LVM will not automatically manage the 'metadataignore' flags. If set to
\fIall\fP, LVM will first clear all of the 'metadataignore' flags on all

2
man/vgcreate.8.in
View File

@ -77,7 +77,7 @@ you should consider some use of \fB--pvmetadatacopies 0\fP as described in
.BR \-\-vgmetadatacopies " " \fINumberOfCopies|unmanaged|all\fP
Sets the desired number of metadata copies in the volume group. If set to
a non-zero value, LVM will automatically manage the 'metadataignore'
flags on the physical volumes (see \fBpvchange --metadataignore\fP) in order
flags on the physical volumes (see \fBpvcreate\fP or \fBpvchange\fP --metadataignore\fP) in order
to achieve \fINumberOfCopies\fP copies of metadata. If set to \fIunmanaged\fP,
LVM will not automatically manage the 'metadataignore' flags. If set to
\fIall\fP, LVM will first clear all of the 'metadataignore' flags on all