mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-22 17:35:59 +03:00
3ab46449f4
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.
33 lines
908 B
Groff
33 lines
908 B
Groff
.TH VGIMPORT 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
|
|
.SH NAME
|
|
vgimport \- make exported volume groups known to the system
|
|
.SH SYNOPSIS
|
|
.B vgimport
|
|
.RB [ \-a | \-\-all ]
|
|
.RB [ \-d | \-\-debug ]
|
|
.RB [ \-h | \-? | \-\-help ]
|
|
.RB [ \-v | \-\-verbose ]
|
|
.I VolumeGroupName
|
|
.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)
|