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

HP-UX Handbook – Rev 13.00 Page 64 (of 110)
Chapter 13 LVM
October 29, 2013
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c0t0d2 8 8
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 ??? 00000 stale /dev/dsk/c0t0d2 00000 current
00001 ??? 00001 stale /dev/dsk/c0t0d2 00001 current
00002 ??? 00002 stale /dev/dsk/c0t0d2 00002 current
00003 ??? 00003 stale /dev/dsk/c0t0d2 00003 current
00004 ??? 00004 stale /dev/dsk/c0t0d2 00004 current
00005 ??? 00005 stale /dev/dsk/c0t0d2 00005 current
00006 ??? 00006 stale /dev/dsk/c0t0d2 00006 current
00007 ??? 00007 stale /dev/dsk/c0t0d2 00007 current
The PV key of a disk indicates its order in the VG. The first PV has the key 0, the
second has the key 1, etc. This does not necessarily have to be the order of
appearance in lvmtab altough it is usually like that, at least when a VG is initially
created.
The PV key can be used to address a PV that is not attached to the VG. This usually
happens if it was not accessible during activation, e.g. due to a hardware or
configuration problem.
NOTE: The PV may be unattached due to some temporary problem during VG
activation which is no longer present. In this case you should try to re-activate the VG to
force LVM to re-scan the devices listed in lvmtab: In this example you can see, that the
LV in question is mirrored. One of its PVs is not attached to the VG, so its device file is
unknown to LVM and displayed as “???”. Addressing this PV is no longer possible using
the device file name. Removing a PV using its PV key
# vgchange -a y vgXX
or
# vgchange -a e vgXX (for exclusively activated Cluster VGs)
If the problem persists follow these steps to clear the situation: