blob: cce31e8f1b580716b0ba4141be0c40aa867b8722 [file] [log] [blame]
.TH VGREDUCE 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
vgreduce \(em reduce a volume group
.B vgreduce
.RB [ \-a | \-\-all ]
.RB [ \-A | \-\-autobackup
.RI { y | n }]
.RB [ \-\-commandprofile
.IR ProfileName ]
.RB [ \-d | \-\-debug ]
.RB [ \-h | \-? | \-\-help ]
.RB [ \-\-removemissing ]
.RB [ \-\-reportformat
.RB { basic | json }]
.RB [ \-t | \-\-test ]
.RB [ \-v | \-\-verbose ]
.I VolumeGroupName
.RI [ PhysicalVolumePath ...]
vgreduce allows you to remove one or more unused physical volumes
from a volume group.
See \fBlvm\fP(8) for common options.
.BR \-a ", " \-\-all
Removes all empty physical volumes if none are given on command line.
.B \-\-removemissing
Removes all missing physical volumes from the volume group, if there are no
logical volumes allocated on those. This resumes normal operation of the volume
group (new logical volumes may again be created, changed and so on).
If this is not possible (there are logical volumes referencing the missing
physical volumes) and you cannot or do not want to remove them manually, you
can run this option with \fB\-\-force\fP to have \fBvgreduce\fP
remove any partial LVs.
Any logical volumes and dependent snapshots that were partly on the
missing disks get removed completely. This includes those parts
that lie on disks that are still present.
If your logical volumes spanned several disks including the ones that are
lost, you might want to try to salvage data first by activating your
logical volumes with \fB\-\-partial\fP as described in \fBlvm\fP(8).
.BR lvm (8),
.BR vgextend (8)