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

HP-UX Handbook – Rev 13.00 Page 53 (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.
If you are setting up a mirrored root config you need have the mirror disk listed in
/stand/bootconf or use mkboot directly to install the ODE files there.
LVM and Serviceguard (Cluster LVM)
In a Serviceguard environment you have one or more VGs that have disks on the
shared bus which can be accessed from multiple systems in the cluster. So it is very
important to guarantee that a VG is active only on one node at a time or you will easily
end up with inconsistant or corrupted data.
A VG that should be accessable from multiple nodes needs special treatment. You have
to ensure that each node has current information about the VG, i.e:
 /etc/lvmtab
 /etc/lvmtab_p
 /dev/vgXX/*
 /etc/lvmconf/vgXX.conf
Any changes to the VG that would affect these files need to be updated to all other
nodes that could potentially activate the VG.
The following table shows which configuration changes affect which files:
configuration change
affects
/etc/lvmtab
/etc/lvmtab_p
/dev/vgXX/
/etc/lvmconf
/
adding/removing a PV from the VG
Yes
No
Yes
adding/removing a LV from the VG
No
Yes
Yes
changing LV/PV characteristics (like
size)
No
No
Yes
Example: Adding a disk to a cluster VG
 On the node where the VG is activated:
1. Add the PV to the VG as usual:
# pvcreate [-f] /dev/rdsk/cXtXdX
# vgextend vgXX /dev/dsk/cXtXdX