2017-02-11 01:20:19 +03:00
lvremove removes one or more LVs. For standard LVs, this returns the
logical extents that were used by the LV to the VG for use by other LVs.
2021-04-16 16:57:01 +03:00
.P
2017-02-11 01:20:19 +03:00
Confirmation will be requested before deactivating any active LV prior to
removal. LVs cannot be deactivated or removed while they are open (e.g.
if they contain a mounted filesystem). Removing an origin LV will also
remove all dependent snapshots.
2021-04-16 16:57:01 +03:00
.P
2017-02-18 00:11:19 +03:00
When a single force option is used, LVs are removed without confirmation,
and the command will try to deactivate unused LVs.
2021-04-16 16:57:01 +03:00
.P
2017-02-18 00:11:19 +03:00
To remove damaged LVs, two force options may be required (\fB-ff\fP).
2021-04-16 16:57:01 +03:00
.P
2017-02-11 01:20:19 +03:00
\fBHistorical LVs\fP
2021-04-16 16:57:01 +03:00
.P
2017-02-11 01:20:19 +03:00
If the configuration setting \fBmetadata/record_lvs_history\fP is enabled
and the LV being removed forms part of the history of at least one LV that
is still present, then a simplified representation of the LV will be
retained. This includes the time of removal (\fBlv_time_removed\fP
reporting field), creation time (\fBlv_time\fP), name (\fBlv_name\fP), LV
uuid (\fBlv_uuid\fP) and VG name (\fBvg_name\fP). This allows later
reporting to see the ancestry chain of thin snapshot volumes, even after
some intermediate LVs have been removed. The names of such historical LVs
acquire a hyphen as a prefix (e.g. '-lvol1') and cannot be reactivated.
Use lvremove a second time, with the hyphen, to remove the record of the
former LV completely.