lvmerge.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

lvmerge(1M) lvmerge(1M)

(Requires Optional HP MirrorDisk/UX Software)

-s If there is no bitmap, do not synchronize the new mirrors in the master_lv_path

after the merge. Using the

-s option may affect data high availability as extents

may remain stale. Use lvsync or vgsync to synchronize the mirrors.

Shared Volume Group Considerations

For volume group version 1.0 and 2.0,

lvmerge cannot be used if the volume group is activated in

shared mode. For volume groups version 2.1 (or higher),

lvmerge 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).

When a node wants to share the volume group, the user must ﬁrst execute a

vgimport if logical volumes

were merged 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.

LANG is not speciﬁed 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

Merge

/dev/vg00/lvol1b

with /dev/vg00/lvol1. Data in /dev/vg00/lvol1b

will be

overwritten by

/dev/vg00/lvol1

and /dev/vg00/lvol1b will be removed.

lvmerge /dev/vg00/lvol1b /dev/vg00/lvol1

Merge /dev/vg01/lvol1b

with /dev/vg01/lvol1. Data in /dev/vg01/lvol1b

will be

overwritten by

/dev/vg01/lvol1

and /dev/vg01/lvol1b will be removed. If the bitmap does

not exist, then mark all extents associated with

/dev/vg01/lvol1b

as stale and complete without

resynchronizing.

lvmerge -s /dev/vg01/lvol1b /dev/vg01/lvol1

WARNINGS

lvmerge does not check to guarantee that the allocation policy of master_lv_path is preserved after the

merge.