summaryrefslogtreecommitdiff
path: root/man/pvcreate.8_pregen
diff options
context:
space:
mode:
authorAlasdair G Kergon <agk@redhat.com>2017-03-28 01:32:59 +0100
committerAlasdair G Kergon <agk@redhat.com>2017-03-28 01:32:59 +0100
commitb9399f21489cb98a21ec08162ba9ac26e4b973c7 (patch)
treeac34ca415f7949adb765f8c89df6bc22634deca3 /man/pvcreate.8_pregen
parent19a72e601f64b21f0587f006f85da058737f077d (diff)
downloadlvm2-b9399f21489cb98a21ec08162ba9ac26e4b973c7.tar.gz
man: pre-generated files weren't committed
Diffstat (limited to 'man/pvcreate.8_pregen')
-rw-r--r--man/pvcreate.8_pregen132
1 files changed, 66 insertions, 66 deletions
diff --git a/man/pvcreate.8_pregen b/man/pvcreate.8_pregen
index 9eb62df48..55d153fef 100644
--- a/man/pvcreate.8_pregen
+++ b/man/pvcreate.8_pregen
@@ -1,6 +1,6 @@
.TH PVCREATE 8 "LVM TOOLS #VERSION#" "Red Hat, Inc."
.SH NAME
-pvcreate \- Initialize physical volume(s) for use by LVM
+pvcreate - Initialize physical volume(s) for use by LVM
.
.SH SYNOPSIS
\fBpvcreate\fP \fIposition_args\fP
@@ -34,63 +34,63 @@ normally prevent it, e.g. if the PV is already in a VG.
.br
.RS 4
.ad l
-[ \fB-f\fP|\fB\-\-force\fP ]
+[ \fB-f\fP|\fB--force\fP ]
.ad b
.br
.ad l
-[ \fB-M\fP|\fB\-\-metadatatype\fP \fBlvm2\fP|\fBlvm1\fP ]
+[ \fB-M\fP|\fB--metadatatype\fP \fBlvm2\fP|\fBlvm1\fP ]
.ad b
.br
.ad l
-[ \fB-u\fP|\fB\-\-uuid\fP \fIString\fP ]
+[ \fB-u\fP|\fB--uuid\fP \fIString\fP ]
.ad b
.br
.ad l
-[ \fB-Z\fP|\fB\-\-zero\fP \fBy\fP|\fBn\fP ]
+[ \fB-Z\fP|\fB--zero\fP \fBy\fP|\fBn\fP ]
.ad b
.br
.ad l
-[ \fB\-\-dataalignment\fP \fISize\fP[k|UNIT] ]
+[ \fB--dataalignment\fP \fISize\fP[k|UNIT] ]
.ad b
.br
.ad l
-[ \fB\-\-dataalignmentoffset\fP \fISize\fP[k|UNIT] ]
+[ \fB--dataalignmentoffset\fP \fISize\fP[k|UNIT] ]
.ad b
.br
.ad l
-[ \fB\-\-bootloaderareasize\fP \fISize\fP[m|UNIT] ]
+[ \fB--bootloaderareasize\fP \fISize\fP[m|UNIT] ]
.ad b
.br
.ad l
-[ \fB\-\-labelsector\fP \fINumber\fP ]
+[ \fB--labelsector\fP \fINumber\fP ]
.ad b
.br
.ad l
-[ \fB\-\-[pv]metadatacopies\fP \fB0\fP|\fB1\fP|\fB2\fP ]
+[ \fB--[pv]metadatacopies\fP \fB0\fP|\fB1\fP|\fB2\fP ]
.ad b
.br
.ad l
-[ \fB\-\-metadatasize\fP \fISize\fP[m|UNIT] ]
+[ \fB--metadatasize\fP \fISize\fP[m|UNIT] ]
.ad b
.br
.ad l
-[ \fB\-\-metadataignore\fP \fBy\fP|\fBn\fP ]
+[ \fB--metadataignore\fP \fBy\fP|\fBn\fP ]
.ad b
.br
.ad l
-[ \fB\-\-norestorefile\fP ]
+[ \fB--norestorefile\fP ]
.ad b
.br
.ad l
-[ \fB\-\-setphysicalvolumesize\fP \fISize\fP[m|UNIT] ]
+[ \fB--setphysicalvolumesize\fP \fISize\fP[m|UNIT] ]
.ad b
.br
.ad l
-[ \fB\-\-reportformat\fP \fBbasic\fP|\fBjson\fP ]
+[ \fB--reportformat\fP \fBbasic\fP|\fBjson\fP ]
.ad b
.br
.ad l
-[ \fB\-\-restorefile\fP \fIString\fP ]
+[ \fB--restorefile\fP \fIString\fP ]
.ad b
.br
[ COMMON_OPTIONS ]
@@ -101,78 +101,78 @@ Common options for lvm:
.
.RS 4
.ad l
-[ \fB-d\fP|\fB\-\-debug\fP ]
+[ \fB-d\fP|\fB--debug\fP ]
.ad b
.br
.ad l
-[ \fB-h\fP|\fB\-\-help\fP ]
+[ \fB-h\fP|\fB--help\fP ]
.ad b
.br
.ad l
-[ \fB-q\fP|\fB\-\-quiet\fP ]
+[ \fB-q\fP|\fB--quiet\fP ]
.ad b
.br
.ad l
-[ \fB-t\fP|\fB\-\-test\fP ]
+[ \fB-t\fP|\fB--test\fP ]
.ad b
.br
.ad l
-[ \fB-v\fP|\fB\-\-verbose\fP ]
+[ \fB-v\fP|\fB--verbose\fP ]
.ad b
.br
.ad l
-[ \fB-y\fP|\fB\-\-yes\fP ]
+[ \fB-y\fP|\fB--yes\fP ]
.ad b
.br
.ad l
-[ \fB\-\-commandprofile\fP \fIString\fP ]
+[ \fB--commandprofile\fP \fIString\fP ]
.ad b
.br
.ad l
-[ \fB\-\-config\fP \fIString\fP ]
+[ \fB--config\fP \fIString\fP ]
.ad b
.br
.ad l
-[ \fB\-\-driverloaded\fP \fBy\fP|\fBn\fP ]
+[ \fB--driverloaded\fP \fBy\fP|\fBn\fP ]
.ad b
.br
.ad l
-[ \fB\-\-longhelp\fP ]
+[ \fB--longhelp\fP ]
.ad b
.br
.ad l
-[ \fB\-\-profile\fP \fIString\fP ]
+[ \fB--profile\fP \fIString\fP ]
.ad b
.br
.ad l
-[ \fB\-\-version\fP ]
+[ \fB--version\fP ]
.ad b
.RE
.SH OPTIONS
.HP
.ad l
-\fB\-\-bootloaderareasize\fP \fISize\fP[m|UNIT]
+\fB--bootloaderareasize\fP \fISize\fP[m|UNIT]
.br
Create a separate bootloader area of specified size besides PV's data
area. The bootloader area is an area of reserved space on the PV from
which LVM will not allocate any extents and it's kept untouched. This is
primarily aimed for use with bootloaders to embed their own data or metadata.
-The start of the bootloader area is always aligned, see also \-\-dataalignment
-and \-\-dataalignmentoffset. The bootloader area size may eventually
+The start of the bootloader area is always aligned, see also --dataalignment
+and --dataalignmentoffset. The bootloader area size may eventually
end up increased due to the alignment, but it's never less than the
size that is requested. To see the bootloader area start and size of
an existing PV use pvs -o +pv_ba_start,pv_ba_size.
.ad b
.HP
.ad l
-\fB\-\-commandprofile\fP \fIString\fP
+\fB--commandprofile\fP \fIString\fP
.br
The command profile to use for command configuration.
See \fBlvm.conf\fP(5) for more information about profiles.
.ad b
.HP
.ad l
-\fB\-\-config\fP \fIString\fP
+\fB--config\fP \fIString\fP
.br
Config settings for the command. These override lvm.conf settings.
The String arg uses the same format as lvm.conf,
@@ -181,50 +181,50 @@ See \fBlvm.conf\fP(5) for more information about config.
.ad b
.HP
.ad l
-\fB\-\-dataalignment\fP \fISize\fP[k|UNIT]
+\fB--dataalignment\fP \fISize\fP[k|UNIT]
.br
Align the start of the data to a multiple of this number.
Also specify an appropriate Physical Extent size when creating a VG.
To see the location of the first Physical Extent of an existing PV,
use pvs -o +pe_start. In addition, it may be shifted by an alignment offset.
-See lvm.conf/data_alignment_offset_detection and \-\-dataalignmentoffset.
+See lvm.conf/data_alignment_offset_detection and --dataalignmentoffset.
.ad b
.HP
.ad l
-\fB\-\-dataalignmentoffset\fP \fISize\fP[k|UNIT]
+\fB--dataalignmentoffset\fP \fISize\fP[k|UNIT]
.br
Shift the start of the data area by this additional offset.
.ad b
.HP
.ad l
-\fB-d\fP|\fB\-\-debug\fP ...
+\fB-d\fP|\fB--debug\fP ...
.br
Set debug level. Repeat from 1 to 6 times to increase the detail of
messages sent to the log file and/or syslog (if configured).
.ad b
.HP
.ad l
-\fB\-\-driverloaded\fP \fBy\fP|\fBn\fP
+\fB--driverloaded\fP \fBy\fP|\fBn\fP
.br
If set to no, the command will not attempt to use device-mapper.
For testing and debugging.
.ad b
.HP
.ad l
-\fB-f\fP|\fB\-\-force\fP ...
+\fB-f\fP|\fB--force\fP ...
.br
Override various checks, confirmations and protections.
Use with extreme caution.
.ad b
.HP
.ad l
-\fB-h\fP|\fB\-\-help\fP
+\fB-h\fP|\fB--help\fP
.br
Display help text.
.ad b
.HP
.ad l
-\fB\-\-labelsector\fP \fINumber\fP
+\fB--labelsector\fP \fINumber\fP
.br
By default the PV is labelled with an LVM2 identifier in its second
sector (sector 1). This lets you use a different sector near the
@@ -233,13 +233,13 @@ in the source). Use with care.
.ad b
.HP
.ad l
-\fB\-\-longhelp\fP
+\fB--longhelp\fP
.br
Display long help text.
.ad b
.HP
.ad l
-\fB\-\-metadataignore\fP \fBy\fP|\fBn\fP
+\fB--metadataignore\fP \fBy\fP|\fBn\fP
.br
Specifies the metadataignore property of a PV.
If yes, metadata areas on the PV are ignored, and lvm will
@@ -248,14 +248,14 @@ If no, lvm will store metadata on the PV.
.ad b
.HP
.ad l
-\fB\-\-metadatasize\fP \fISize\fP[m|UNIT]
+\fB--metadatasize\fP \fISize\fP[m|UNIT]
.br
The approximate amount of space used for each VG metadata area.
The size may be rounded.
.ad b
.HP
.ad l
-\fB-M\fP|\fB\-\-metadatatype\fP \fBlvm2\fP|\fBlvm1\fP
+\fB-M\fP|\fB--metadatatype\fP \fBlvm2\fP|\fBlvm1\fP
.br
Specifies the type of on-disk metadata to use.
\fBlvm2\fP (or just \fB2\fP) is the current, standard format.
@@ -264,21 +264,21 @@ can be used for accessing old data.
.ad b
.HP
.ad l
-\fB\-\-norestorefile\fP
+\fB--norestorefile\fP
.br
-In conjunction with \-\-uuid, this allows a uuid to be specified
+In conjunction with --uuid, this allows a uuid to be specified
without also requiring that a backup of the metadata be provided.
.ad b
.HP
.ad l
-\fB\-\-profile\fP \fIString\fP
+\fB--profile\fP \fIString\fP
.br
-An alias for \-\-commandprofile or \-\-metadataprofile, depending
+An alias for --commandprofile or --metadataprofile, depending
on the command.
.ad b
.HP
.ad l
-\fB\-\-[pv]metadatacopies\fP \fB0\fP|\fB1\fP|\fB2\fP
+\fB--[pv]metadatacopies\fP \fB0\fP|\fB1\fP|\fB2\fP
.br
The number of metadata areas to set aside on a PV for storing VG metadata.
When 2, one copy of the VG metadata is stored at the front of the PV
@@ -291,14 +291,14 @@ on the ability to use vgsplit later.)
.ad b
.HP
.ad l
-\fB-q\fP|\fB\-\-quiet\fP ...
+\fB-q\fP|\fB--quiet\fP ...
.br
-Suppress output and log messages. Overrides \-\-debug and \-\-verbose.
+Suppress output and log messages. Overrides --debug and --verbose.
Repeat once to also suppress any prompts with answer no.
.ad b
.HP
.ad l
-\fB\-\-reportformat\fP \fBbasic\fP|\fBjson\fP
+\fB--reportformat\fP \fBbasic\fP|\fBjson\fP
.br
Overrides current output format for reports which is defined globally by
the report/output_format setting in lvm.conf.
@@ -309,9 +309,9 @@ output in JSON format. See \fBlvmreport\fP(7) for more information.
.ad b
.HP
.ad l
-\fB\-\-restorefile\fP \fIString\fP
+\fB--restorefile\fP \fIString\fP
.br
-In conjunction with \-\-uuid, this reads the file (produced by
+In conjunction with --uuid, this reads the file (produced by
vgcfgbackup), extracts the location and size of the data on the PV,
and ensures that the metadata produced by the program is consistent
with the contents of the file, i.e. the physical extents will be in
@@ -321,14 +321,14 @@ areas. Use with care.
.ad b
.HP
.ad l
-\fB\-\-setphysicalvolumesize\fP \fISize\fP[m|UNIT]
+\fB--setphysicalvolumesize\fP \fISize\fP[m|UNIT]
.br
Overrides the automatically detected size of the PV.
Use with care, or prior to reducing the physical size of the device.
.ad b
.HP
.ad l
-\fB-t\fP|\fB\-\-test\fP
+\fB-t\fP|\fB--test\fP
.br
Run in test mode. Commands will not update metadata.
This is implemented by disabling all metadata writing but nevertheless
@@ -338,33 +338,33 @@ back metadata it believes has changed but hasn't.
.ad b
.HP
.ad l
-\fB-u\fP|\fB\-\-uuid\fP \fIString\fP
+\fB-u\fP|\fB--uuid\fP \fIString\fP
.br
Specify a UUID for the device.
Without this option, a random UUID is generated.
This option is needed before restoring a backup of LVM metadata
onto a replacement device; see vgcfgrestore(8). As such, use of
-\-\-restorefile is compulsory unless the \-\-norestorefile is used.
+--restorefile is compulsory unless the --norestorefile is used.
All PVs must have unique UUIDs, and LVM will prevent certain operations
if multiple devices are seen with the same UUID.
See vgimportclone(8) for more information.
.ad b
.HP
.ad l
-\fB-v\fP|\fB\-\-verbose\fP ...
+\fB-v\fP|\fB--verbose\fP ...
.br
Set verbose level. Repeat from 1 to 4 times to increase the detail
of messages sent to stdout and stderr.
.ad b
.HP
.ad l
-\fB\-\-version\fP
+\fB--version\fP
.br
Display version information.
.ad b
.HP
.ad l
-\fB-y\fP|\fB\-\-yes\fP
+\fB-y\fP|\fB--yes\fP
.br
Do not prompt for confirmation interactively but always assume the
answer yes. Use with extreme caution.
@@ -372,11 +372,11 @@ answer yes. Use with extreme caution.
.ad b
.HP
.ad l
-\fB-Z\fP|\fB\-\-zero\fP \fBy\fP|\fBn\fP
+\fB-Z\fP|\fB--zero\fP \fBy\fP|\fBn\fP
.br
Controls if the first 4 sectors (2048 bytes) of the device are wiped.
The default is to wipe these sectors unless either or both of
-\-\-restorefile or \-\-uuid are specified.
+--restorefile or --uuid are specified.
.ad b
.SH VARIABLES
.HP
@@ -404,7 +404,7 @@ UNIT represents other possible input units: \fBbBsSkKmMgGtTpPeE\fP.
b|B is bytes, s|S is sectors of 512 bytes, k|K is kilobytes,
m|M is megabytes, g|G is gigabytes, t|T is terabytes,
p|P is petabytes, e|E is exabytes.
-(This should not be confused with the output control \-\-units, where
+(This should not be confused with the output control --units, where
capital letters mean multiple of 1000.)
.SH ENVIRONMENT VARIABLES
See \fBlvm\fP(8) for information about environment variables used by lvm.
@@ -420,7 +420,7 @@ partitioning (sector 7 is the lowest aligned logical block, the 4KiB
sectors start at LBA -1, and consequently sector 63 is aligned on a 4KiB
boundary) manually account for this when initializing for use by LVM.
.br
-.B pvcreate \-\-dataalignmentoffset 7s /dev/sdb
+.B pvcreate --dataalignmentoffset 7s /dev/sdb
.SH SEE ALSO
.BR lvm (8)