HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 71 (of 108)
Chapter 15 Serviceguard
October 29, 2013
LVM related Problems
The predominant causes of LVM problems are incorrect content of /etc/lvmtab (or lvmtab_p) on
each node, or incorrect activation mode assigned to a given volume group.
Example 1
If a disk is missing from lvmtab on one node, cmcheckconf may fail with:
ERROR: Volume group vgA is configured differently on node Node1 than on node
Node2.
If an admin adds a disk to a VG on one node, the lvmtab files on the other nodes become out of
date until the admin resolves the problem. The fastest way is to use a map file containing the
VGID, then using vgexport and vgimport to re-load the volume group LUN list to lvmtab.
The message may take on a warning mode instead, if only Pvlinks are missing from lvmtab on a
given node.
Example 2
If an admin fails to add a VOLUME_GROUP parameter to the cluster ASCII file and attempts to
start a package that attempts to activate that VG, the package log will record something like this:
Error: vgchange: Activation mode requested for the volume group "/dev/vg03"
conflicts with configured mode.
Example 3
Errors: Volume group vgA currently belongs to another cluster. First cluster lock volume group
vgA belongs to another cluster. Second cluster lock volume group vgB belongs to another
cluster.
The LVM header of that volume group contains the cluster ID of a different cluster. If you are
sure that your cluster should own these disks you can perform
# vgchange -c n <VG>
to clear the ID. This command should be performed on node on witch the VG is active.
Example 4
Warning: The disk at XXX on node Node1 does not have an ID.
Serviceguard prints warning messages for all disks that do not contain a valid header. This is
normal and can be ignored for all disks that are not part of a LVM volume group or VxVM disk
group.
Example 5
Error: Unable to determine a unique identifier for physical volume vgA on
node Node1.
An attempt to read a valid PVID from the listed device failed. Check if the device is readable and