diff options
| author | Jonathan Brassow <jbrassow@redhat.com> | 2013-02-20 16:28:26 -0600 |
|---|---|---|
| committer | Jonathan Brassow <jbrassow@redhat.com> | 2013-02-20 16:37:41 -0600 |
| commit | 3ab46449f4dbcc45fe878149838a8439f5ac8b34 (patch) | |
| tree | a7fbd62107fbd8aed4d7fc7155b04b0daef87889 /man | |
| parent | 303e86adc8dbbab2fe78412f1b90021e5bdb5bc3 (diff) | |
| download | lvm2-3ab46449f4dbcc45fe878149838a8439f5ac8b34.tar.gz | |
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.
Diffstat (limited to 'man')
| -rw-r--r-- | man/vgimport.8.in | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/man/vgimport.8.in b/man/vgimport.8.in index dd781dea8..9496d4067 100644 --- a/man/vgimport.8.in +++ b/man/vgimport.8.in @@ -20,6 +20,11 @@ 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), |