HP-UX HB v13.00 Ch-13 - LVM

HP-UX Handbook – Rev 13.00 Page 74 (of 110)
Chapter 13 LVM
October 29, 2013
NOTE: “lifload –f updatediaglif” performs “mkboot -b updatediaglif -p ISL -p
HPUX /dev/rdsk/cXtXdX”, where cXtXdX are all the disks listed in
/stand/bootconf.
The –p option of mkboot preserves the specified file so that it is not
overwritten in LIF.
Refer to section Offline Diagnostics (ODE) if you have problems with this.
4. Write content of LABEL file, i.e set root, boot, swap and dump device:
NOTE:This step can be omitted if you replace a failed mirror disk. Then this
information has already been restored by vgcfgrestore. To be sure to have
the latest information on the disk just do the following steps.
# lvlnboot -r /dev/<rootVG>/lvol3
# lvlnboot -b /dev/<rootVG>/lvol1
# lvlnboot -s /dev/<rootVG>/lvol2
# lvlnboot -d /dev/<rootVG>/lvol2
# lvlnboot –v (to ckeck it)
What is the new in 11.31 regarding LVM
Native Multipathing in LVM
In HP-UX 11i v3 LVM supports both legacy and persistent DSFs(persistent DSFs are a
new type of DSFs. More about them, can be found in the I/O Chapter of this book,
under section “New Type of DSFs”).
A volume group can be configured, using both types of DSFs. Some volume groups can
use legacy device special files, some can use persistent, and some can use a mixture
of both types. Suporting a mixed mode configuration allows a volume group that
currently uses one DSF naming model to be extended (by vgextend) with the same or
another physical volume using a different DSF naming model. Such operations result in
a mixed mode volume group and facilitate a phased DSF migration from legacy to agile
naming model. The /etc/lvmtab looks in the following way when having a mixed mode
supported:
Example:
strings /etc/lvmtab
/dev/vg00
/dev/disk/disk6_p2
/dev/disk/disk5