lvextend.1m (2010 09)

l
lvextend(1M) lvextend(1M)
Data in the new copies is synchronized unless the
-s option is specified.
The synchronization process can be time consuming, depending on
hardware characteristics and the amount of data.
One, and only one,
-l, -L,or
-m option must be specified. (The -m
option is not applicable for snapshot volumes.)
-s Do not synchronize the new mirror copies. This may affect data high
availability so use lvsync or vgsync to synchronize the mirrors.
The
-m option must be specified along with this option. (The
-m and -s
options are not applicable for snapshot volumes.)
Striped Logical Volume considerations
Striped and mirrored logical volumes are supported.
An increase in size of a striped logical volume is done by increments of stripes logical extents. One incre-
ment corresponds to stripes physical extents if the volume is not mirrored or to stripes *(mirror_copies +
1) physical extents if the volume is mirrored.
stripes is the number of disks the logical volume is striped across. It is set with the option
-i stripes of
the
lvcreate command.
mirror_copies is the number of mirror copies allocated for each extent. It is set with the
-m option of the
lvcreate and lvextend commands.
LVM striped logical volumes are always allocated using the strict or PVG-strict allocation policies. Each
physical extent of an increment is allocated on a different physical volume in the volume group.
A size increase of a striped volume requires at least stripes (or stripes *(mirror_copies + 1) if the volume
is mirrored) physical volumes with adequate free space and meeting the allocation policy.
An increase of the number of mirror copies of a striped volume requires at least (stripes times the number
of copies to add) physical volumes with adequate free space and meeting the allocation policy.
Shared Volume Group Considerations
For volume group version 1.0 and 2.0,
lvextend cannot be used if the volume group is activated in
shared mode. For volume groups version 2.1 (or higher), lvextend 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).
If physical volume groups are passed as arguments,
lvextend uses the physical volume group file
(/etc/lvmpvg) of the system where the command is issued (the server).
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
Increase the number of the logical extents of a logical volume to 100:
lvextend -l 100 /dev/vg01/lvol3
Increase the logical volume size to 400 MB:
lvextend -L 400 /dev/vg01/lvol4
Increase the logical extents of a snapshot volume to 50:
lvextend -l 50 /dev/vg01/lvol4_S5
Allocate two mirrors (that is, two copies of the original) for each logical extent of a logical volume:
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3