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

HP-UX Handbook – Rev 13.00 Page 105 (of 110)
Chapter 13 LVM
October 29, 2013
Quorum Problems
Quorum Problems with a Non-Root Volume Group
If you attempt to activate a non-root volume group when not enough disks are present
to establish a quorum, you will see error messages similar to those in this example:
# vgchange –a y /dev/vg01
vgchange: Warning: Couldn't attach to the volume group
physical volume "/dev/dsk/c1t0d2":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Couldn't activate volume group "/dev/vg01":
Either no physical volumes are attached or no valid VGDAs were found
on the physical volumes.
If a non-root volume group does not get activated because of a failure to meet quorum,
try the following:
 Check the power and data connections of all the disks that are part of the volume
group that you cannot activate. Return all disks (or, at least enough to make a
quorum) to service. Then, use the vgchange command to try to activate the
volume group again.
 If there is no other way to make a quorum available, the -q option to the
vgchange command will override the quorum check.
EXAMPLE:
# vgchange –a y –q n /dev/vg01
CAUTION: This will activate the volume group but a quorum will not be present. You
might get messages about not being able to access logical volumes. This is because
some or all of a logical volume might be located on one of the disks that is not present.
Whenever you override a quorum requirement, you run the risk of using data that is not
current. Be sure to check the data on the logical volumes in the activated volume group
as well as the size and locations of the logical volumes to ensure that they are up-to-
date.
You should attempt to return the disabled disks to the volume group as soon as
possible. When you return a disk to service that was not online when you originally
activated the volume group, use the activation command again to attach the now
accessible disks to the volume group.