lvm2/man/vgimport.8.in

.TH VGIMPORT 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
.SH NAME
vgimport \(em make exported volume groups known to the system
.SH SYNOPSIS
.B vgimport
.RB [ \-a | \-\-all ]
.RB [ \-d | \-\-debug ]
.RB [ \-h | \-? | \-\-help ]
.RB [ \-S | \-\-select
.IR Selection ]
.RB [ \-v | \-\-verbose ]
.RI [ VolumeGroupName ...]
.SH DESCRIPTION
vgimport allows you to make a Volume Group that was previously
exported using
.BR vgexport (8)
known to the system again, perhaps after moving its Physical Volumes
from a different machine.
.SH OPTIONS
See \fBlvm\fP(8) for common options.
.TP
.BR \-a ", " \-\-all
Import all exported Volume Groups.
.TP
.BR \-\-force
Import exported Volume Groups even if there are missing Physical Volumes.
This option should only be used if the missing devices are known to have
failed and they cannot be restored.
.SH SEE ALSO
.BR lvm (8),
.BR pvscan (8),
.BR vgexport (8),
.BR vgscan (8)
Generate man pages from templates and include version. (romster) 2008-10-08 16:50:13 +04:00			`.TH VGIMPORT 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -- nroff --`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.SH NAME`
man: properly escape - Dash should be using '\' to be typographically correct. 2014-06-11 13:06:30 +04:00			`vgimport \(em make exported volume groups known to the system`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.SH SYNOPSIS`
			`.B vgimport`
Update man pages Use one style for man pages. 2012-04-11 16:42:10 +04:00			`.RB [ \-a \| \-\-all ]`
			`.RB [ \-d \| \-\-debug ]`
			`.RB [ \-h \| \-? \| \-\-help ]`
man: reference -S/--select in {vg,lv,pv}change, {vg,lv}remove, {vg,lv,pv}display and vg{import,export} man pages 2015-02-11 12:03:37 +03:00			`.RB [ \-S \| \-\-select`
			`.IR Selection ]`
Update man pages Use one style for man pages. 2012-04-11 16:42:10 +04:00			`.RB [ \-v \| \-\-verbose ]`
			`.RI [ VolumeGroupName ...]`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.SH DESCRIPTION`
Update man pages Use one style for man pages. 2012-04-11 16:42:10 +04:00			`vgimport allows you to make a Volume Group that was previously`
			`exported using`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.BR vgexport (8)`
			`known to the system again, perhaps after moving its Physical Volumes`
			`from a different machine.`
			`.SH OPTIONS`
Update man pages Use one style for man pages. 2012-04-11 16:42:10 +04:00			`See \fBlvm\fP(8) for common options.`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.TP`
Update man pages Use one style for man pages. 2012-04-11 16:42:10 +04:00			`.BR \-a ", " \-\-all`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`Import all exported Volume Groups.`
vgimport: Allow '--force' to import VGs with missing PVs. When there are missing PVs in a volume group, most operations that alter the LVM metadata are disallowed. It turns out that 'vgimport' is one of those disallowed operations. This is bad because it creates a circular dependency. 'vgimport' will complain that the VG is inconsistent and that 'vgreduce --removemissing' must be run. However, 'vgreduce' cannot be run because it has not been imported. Therefore, 'vgimport' must be one of the operations allowed to change the metadata when PVs are missing. The '--force' option is the way to make 'vgimport' happen in spite of the missing PVs. 2013-02-21 02:28:26 +04:00			`.TP`
			`.BR \-\-force`
			`Import exported Volume Groups even if there are missing Physical Volumes.`
			`This option should only be used if the missing devices are known to have`
			`failed and they cannot be restored.`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.SH SEE ALSO`
Generate man pages from templates and include version. (romster) 2008-10-08 16:50:13 +04:00			`.BR lvm (8),`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.BR pvscan (8),`
Generate man pages from templates and include version. (romster) 2008-10-08 16:50:13 +04:00			`.BR vgexport (8),`
Add/update some man pages. 2003-11-14 19:17:55 +03:00			`.BR vgscan (8)`