{"id":3584,"date":"2022-12-20T17:09:05","date_gmt":"2022-12-20T20:09:05","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/vgextend-man8\/"},"modified":"2022-12-20T17:09:05","modified_gmt":"2022-12-20T20:09:05","slug":"vgextend-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/vgextend-man8\/","title":{"rendered":"VGEXTEND (man8)"},"content":{"rendered":"

VGEXTEND<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
USAGE<\/a>
OPTIONS<\/a>
VARIABLES<\/a>
ENVIRONMENT VARIABLES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

vgextend \u2212 Add physical volumes to a volume group<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

vgextend<\/b> position_args<\/i>
[ option_args<\/i> ]<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

vgextend adds one or more PVs to a VG. This increases the space available for LVs in the VG.<\/p>\n

Also, PVs that have gone missing and then returned, e.g. due to a transient device failure, can be added back to the VG without re-initializing them (see \u2212\u2212restoremissing).<\/p>\n

If the specified PVs have not yet been initialized with pvcreate, vgextend will initialize them. In this case pvcreate options can be used, e.g. -\u2212labelsector, \u2212\u2212metadatasize, \u2212\u2212metadataignore, -\u2212pvmetadatacopies, \u2212\u2212dataalignment, \u2212\u2212dataalignmentoffset.<\/p>\n

USAGE <\/a> <\/h2>\n

vgextend<\/b> VG PV<\/i> …<\/p>\n

[ \u2212A<\/b>|\u2212\u2212autobackup y<\/b>|n<\/b> ]
[ \u2212f<\/b>|\u2212\u2212force<\/b> ]
[ \u2212Z<\/b>|\u2212\u2212zero y<\/b>|n<\/b> ]
[ \u2212M<\/b>|\u2212\u2212metadatatype lvm2<\/b> ]
[ \u2212\u2212labelsector<\/b> Number<\/i> ]
[ \u2212\u2212metadatasize<\/b> Size<\/i>[m|UNIT] ]
[ \u2212\u2212pvmetadatacopies 0<\/b>|1<\/b>|2<\/b> ]
[ \u2212\u2212metadataignore y<\/b>|n<\/b> ]
[ \u2212\u2212dataalignment<\/b> Size<\/i>[k|UNIT] ]
[ \u2212\u2212dataalignmentoffset<\/b> Size<\/i>[k|UNIT] ]
[ \u2212\u2212reportformat basic<\/b>|json<\/b> ]
[ \u2212\u2212restoremissing<\/b> ]
[ COMMON_OPTIONS ]<\/p>\n

Common options for lvm:<\/p>\n

[ \u2212d<\/b>|\u2212\u2212debug<\/b> ]
[ \u2212h<\/b>|\u2212\u2212help<\/b> ]
[ \u2212q<\/b>|\u2212\u2212quiet<\/b> ]
[ \u2212t<\/b>|\u2212\u2212test<\/b> ]
[ \u2212v<\/b>|\u2212\u2212verbose<\/b> ]
[ \u2212y<\/b>|\u2212\u2212yes<\/b> ]
[ \u2212\u2212commandprofile<\/b> String<\/i> ]
[ \u2212\u2212config<\/b> String<\/i> ]
[ \u2212\u2212driverloaded y<\/b>|n<\/b> ]
[ \u2212\u2212lockopt<\/b> String<\/i> ]
[ \u2212\u2212longhelp<\/b> ]
[ \u2212\u2212nolocking<\/b> ]
[ \u2212\u2212profile<\/b> String<\/i> ]
[ \u2212\u2212version<\/b> ]<\/p>\n

OPTIONS <\/a> <\/h2>\n\n\n
<\/td>\n\n

\u2212A<\/b>|\u2212\u2212autobackup y<\/b>|n<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Specifies if metadata should be backed up automatically after a change. Enabling this is strongly advised! See vgcfgbackup<\/b>(8) for more information.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212commandprofile<\/b> String<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

The command profile to use for command configuration. See lvm.conf<\/b>(5) for more information about profiles.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212config<\/b> String<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Config settings for the command. These override lvm.conf settings. The String arg uses the same format as lvm.conf, or may use section\/field syntax. See lvm.conf<\/b>(5) for more information about config.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212dataalignment<\/b> Size<\/i>[k|UNIT]<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Align the start of a PV data area with a multiple of this number. To see the location of the first Physical Extent (PE) of an existing PV, use pvs \u2212o +pe_start. In addition, it may be shifted by an alignment offset, see \u2212\u2212dataalignmentoffset. Also specify an appropriate PE size when creating a VG.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212dataalignmentoffset<\/b> Size<\/i>[k|UNIT]<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Shift the start of the PV data area by this additional offset.<\/p>\n\n\n
<\/td>\n\n

\u2212d<\/b>|\u2212\u2212debug<\/b> …<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

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).<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212driverloaded y<\/b>|n<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

If set to no, the command will not attempt to use device-mapper. For testing and debugging.<\/p>\n\n\n
<\/td>\n\n

\u2212f<\/b>|\u2212\u2212force<\/b> …<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Override various checks, confirmations and protections. Use with extreme caution.<\/p>\n\n\n
<\/td>\n\n

\u2212h<\/b>|\u2212\u2212help<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Display help text.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212labelsector<\/b> Number<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

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 start of the disk (between 0 and 3 inclusive \u2212 see LABEL_SCAN_SECTORS in the source). Use with care.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212lockopt<\/b> String<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Used to pass options for special cases to lvmlockd. See lvmlockd<\/b>(8) for more information.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212longhelp<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Display long help text.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212metadataignore y<\/b>|n<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Specifies the metadataignore property of a PV. If yes, metadata areas on the PV are ignored, and lvm will not store metadata in the metadata areas of the PV. If no, lvm will store metadata on the PV.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212metadatasize<\/b> Size<\/i>[m|UNIT]<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

The approximate amount of space used for each VG metadata area. The size may be rounded.<\/p>\n\n\n
<\/td>\n\n

\u2212M<\/b>|\u2212\u2212metadatatype lvm2<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Specifies the type of on-disk metadata to use. lvm2<\/b> (or just 2<\/b>) is the current, standard format. lvm1<\/b> (or just 1<\/b>) is no longer used.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212nolocking<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Disable locking.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212profile<\/b> String<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

An alias for \u2212\u2212commandprofile or \u2212\u2212metadataprofile, depending on the command.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212pvmetadatacopies 0<\/b>|1<\/b>|2<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

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 and a second copy is stored at the end. When 1, one copy of the VG metadata is stored at the front of the PV. When 0, no copies of the VG metadata are stored on the given PV. This may be useful in VGs containing many PVs (this places limitations on the ability to use vgsplit later.)<\/p>\n\n\n
<\/td>\n\n

\u2212q<\/b>|\u2212\u2212quiet<\/b> …<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Suppress output and log messages. Overrides \u2212\u2212debug and \u2212\u2212verbose. Repeat once to also suppress any prompts with answer \u2019no\u2019.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212reportformat basic<\/b>|json<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Overrides current output format for reports which is defined globally by the report\/output_format setting in lvm.conf. basic<\/b> is the original format with columns and rows. If there is more than one report per command, each report is prefixed with the report name for identification. json<\/b> produces report output in JSON format. See lvmreport<\/b>(7) for more information.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212restoremissing<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Add a PV back into a VG after the PV was missing and then returned, e.g. due to a transient failure. The PV is not reinitialized.<\/p>\n\n\n
<\/td>\n\n

\u2212t<\/b>|\u2212\u2212test<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Run in test mode. Commands will not update metadata. This is implemented by disabling all metadata writing but nevertheless returning success to the calling function. This may lead to unusual error messages in multi-stage operations if a tool relies on reading back metadata it believes has changed but hasn\u2019t.<\/p>\n\n\n
<\/td>\n\n

\u2212v<\/b>|\u2212\u2212verbose<\/b> …<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212version<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Display version information.<\/p>\n\n\n
<\/td>\n\n

\u2212y<\/b>|\u2212\u2212yes<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Do not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see \u2212qq.)<\/p>\n\n\n
<\/td>\n\n

\u2212Z<\/b>|\u2212\u2212zero y<\/b>|n<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

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 -\u2212restorefile or \u2212\u2212uuid are specified.<\/p>\n\n\n

VARIABLES <\/a> <\/h2>\n

\n
<\/td>\n<\/td>\n <\/td>\n<\/tr>\n
<\/td>\n\n

VG<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Volume Group name. See lvm<\/b>(8) for valid names.<\/p>\n\n\n
<\/td>\n\n

PV<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Physical Volume name, a device path under \/dev. For commands managing physical extents, a PV positional arg generally accepts a suffix indicating a range (or multiple ranges) of physical extents (PEs). When the first PE is omitted, it defaults to the start of the device, and when the last PE is omitted it defaults to end. Start and end range (inclusive): PV<\/i>[:<\/b>PE<\/i>\u2212<\/b>PE<\/i>]… Start and length range (counting from 0): PV<\/i>[:<\/b>PE<\/i>+<\/b>PE<\/i>]…<\/p>\n\n\n
<\/td>\n\n

String<\/i><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

See the option description for information about the string content.<\/p>\n\n\n
<\/td>\n\n

Size<\/i>[UNIT]<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Size is an input number that accepts an optional unit. Input units are always treated as base two values, regardless of capitalization, e.g. \u2019k\u2019 and \u2019K\u2019 both refer to 1024. The default input unit is specified by letter, followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE<\/b>. 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 \u2212\u2212units, where capital letters mean multiple of 1000.)<\/p>\n

ENVIRONMENT VARIABLES <\/a> <\/h2>\n

See lvm<\/b>(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter.<\/p>\n

EXAMPLES <\/a> <\/h2>\n

Add two PVs to a VG.
vgextend vg00 \/dev\/sda4 \/dev\/sdn1<\/b><\/p>\n

SEE ALSO <\/a> <\/h2>\n

lvm<\/b>(8) lvm.conf<\/b>(5) lvmconfig<\/b>(8)<\/p>\n

pvchange<\/b>(8) pvck<\/b>(8) pvcreate<\/b>(8) pvdisplay<\/b>(8) pvmove<\/b>(8) pvremove<\/b>(8) pvresize<\/b>(8) pvs<\/b>(8) pvscan<\/b>(8)<\/p>\n

vgcfgbackup<\/b>(8) vgcfgrestore<\/b>(8) vgchange<\/b>(8) vgck<\/b>(8) vgcreate<\/b>(8) vgconvert<\/b>(8) vgdisplay<\/b>(8) vgexport<\/b>(8) vgextend<\/b>(8) vgimport<\/b>(8) vgimportclone<\/b>(8) vgmerge<\/b>(8) vgmknodes<\/b>(8) vgreduce<\/b>(8) vgremove<\/b>(8) vgrename<\/b>(8) vgs<\/b>(8) vgscan<\/b>(8) vgsplit<\/b>(8)<\/p>\n

lvcreate<\/b>(8) lvchange<\/b>(8) lvconvert<\/b>(8) lvdisplay<\/b>(8) lvextend<\/b>(8) lvreduce<\/b>(8) lvremove<\/b>(8) lvrename<\/b>(8) lvresize<\/b>(8) lvs<\/b>(8) lvscan<\/b>(8)<\/p>\n

lvm-fullreport<\/b>(8) lvm-lvpoll<\/b>(8) lvm2\u2212activation\u2212generator<\/b>(8) blkdeactivate<\/b>(8) lvmdump<\/b>(8)<\/p>\n

dmeventd<\/b>(8) lvmpolld<\/b>(8) lvmlockd<\/b>(8) lvmlockctl<\/b>(8) cmirrord<\/b>(8) lvmdbusd<\/b>(8)<\/p>\n

lvmsystemid<\/b>(7) lvmreport<\/b>(7) lvmraid<\/b>(7) lvmthin<\/b>(7) lvmcache<\/b>(7)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

vgextend \u2212 Add physical volumes to a volume group <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,701],"class_list":["post-3584","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-vgextend"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3584","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3584"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3584\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}