vgreduce.1m (2010 09)

v
vgreduce(1M) vgreduce(1M)
For missing PVs which have extents in use by logical volumes that are not
snapshots, you must free up all the extents by using the
lvreduce or lvremove
commands (see lvreduce (1M) and lvremove (1M)) and re-run
vgreduce with the -
f option.
For missing PVs which have extents in use by snapshot logical volumes, you must
free up all the extents by using the
lvremove command (see lvremove (1M)) and
re-run
vgreduce with the -f option.
For missing PVs which have pre-allocated extents, you must free up all such extents
by using the
lvremove command (see lvremove (1M)) and re-run
vgreduce with
the
-f option.
This option is most commonly used when the
vgdisplay command (see
vgdisplay (1M)) shows "Cur PV" higher than "Act PV" and all of the PVs belonging to
the volume group are attached. This option only works on PVs and not on links.
See the
-l option for details on handling missing links.
-l pv_path Removes the specified pv_path/s from the
lvmtab or lvmtab_p file. This task
will only be performed if the pv_path is currently marked as missing from the
volume group. This option was mainly designed for the problem where the
vgscan
or the vgimport command place too many links beyond the max limit allowed in
the lvmtab or lvmtab_p file. Currently the max limit is 8 paths to a PV (seven
alternates and one primary). In this situation, invoking the command without the
-f option will not resolve the condition because the path is not attached to the
volume group. Similarly, this condition can not be overcome by invoking with the
-f option, as the same works on physical volumes rather than the links.
pv_path The block device path name of a physical volume.
vg_name The path name of the volume group.
Shared Volume Group Considerations
For volume group version 1.0 and 2.0,
vgreduce cannot be used if the volume group is activated in
shared mode. For volume groups version 2.1 (or higher), vgreduce can be performed when activated in
either shared, exclusive, or standalone mode.
Note that the
lvmpud daemon must be running on all the nodes sharing a volume group activated in
shared mode. See lvmpud (1M).
In the case a PV alternate link is reduced,
/etc/lvmtab_p
is updated only on the server node. In the
case a PV is reduced, all the PV device special files are removed from
/etc/lvmtab_p
on all the nodes
sharing the volume group.
When a node wants to share the volume group, the user must first execute a
vgimport if physical
volumes were removed at the time the volume group was not activated on that node.
LVM shared mode is currently only available in Serviceguard clusters.
EXTERNAL INFLUENCES
Environment Variables
LANG determines the language in which messages are displayed.
If
LANG is not specified or is null, it defaults to "C" (see lang (5)).
If any internationalization variable contains an invalid setting, all internationalization variables default
to "C" (see environ (5)).
EXAMPLES
Remove physical volume
/dev/dsk/c0t1d0 from volume group /dev/vg01:
vgreduce /dev/vg01 /dev/dsk/c0t1d0
Force, reduction of missing PVs from volume group: vg01
vgreduce -f /dev/vg01
The following messages will appear after missing PVs has been removed successfully:
PV with key 0 successfully deleted from vg
/dev/vg01
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010