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

HP-UX Handbook – Rev 13.00 Page 95 (of 110)
Chapter 13 LVM
October 29, 2013
NIKE/LVM limitation issue. It's important to quiesce the logical
volume's I/O before re-constructing the /etc/lvmtab.
If for some reason, there is a need to re-construct /etc/lvmtab when
the system is running production application, vgscan will create a
partial /etc/lvmtab. In this case, most of the primary paths should
be included in the /etc/lvmtab. Use vgextend to include any missing
alternate paths in the VG.
If the preview mode has no errors, continue with
/usr/sbin/vgscan
Check /etc/lvmtab with
strings /etc/lvmtab
vgchange
1. PROBLEM – vgchange returns “cross device link”
After replacing a bad disk in a mirrored pair in a VG (vg02) that belonged to
Serviceguard pkg, activation of vg02 fails even after vgcfgrestore to both pri and mirror
disks.
vgchange -a y /dev/vg02 gives error "cross device link"
RESOLUTION
First one must test activation on the other node or nodes that share this VG in
Serviceguard. Success of activation on those nodes means the problem is not with the
disks and their LVM headers but with local OS information on the node where the
problem exists, either lvmtab, /dev/vgname, or corruption with LVM in memory.
Second, one needs to try and go through all the standard methods to fix that error
"cross device link". Here are the possible solutions:
If that does not work, then we can try using vgscan. So one can try to move /etc/lvmtab
to /etc/lvmtab.keep and run vgscan.
# mv /etc/lvmtab /etc/lvmtab.keep
# vgscan -va
# vgchange -a y /dev/vgname