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

HP-UX Handbook – Rev 13.00 Page 96 (of 110)
Chapter 13 LVM
October 29, 2013
If that fails, one can try to reimport using map file from any other node where activation
works. On one of those nodes, one can get a good copy of such map file for that VG
using:
# vgexport -pvs -m mapfile /dev/vgname
Then one must rcp or ftp that mapfile to the node that is having the problem. There one
can try to re-import that VG to see if problem is resolved:
# cp /etc/lvmtab.keep /etc/lvmtab copies back original lvmtab
# vgexport -v /dev/vgname
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xNM0000
# vgimport -vs -m mapfile /dev/vgname
# vgchange -a y /dev/vgname
Here the minor number 0xNM0000 where NM=unique two digit hex integer, such as 01,
or 02 or 5C (limited in value to the kernel parameter maxvgs). If that fails, one can try to
reimport the VG using the dev files of the disks that should be in that VG. You can do
strings on /etc/lvmtab to see those dev files. But one needs to edit the mapfile and
remove the first line that has VGID in it:
# cp /etc/lvmtab.keep /etc/lvmtab
# strings /etc/lvmtab <<<< see which disks are under that VG
# vgexport -v /dev/vgname
# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xNM0000
# vi mapfile <<<< remove VGID line and save it
# export D=/dev/dsk
# vgimport -v -m mapfile /dev/vgname $D/disk1 $D/disk2 .. $D/diskN
# vgchange -a y /dev/vgname
Where diskM=cXtYdZ for a given disk in the VG, so that $D/c0t6d0 is really
/dev/dsk/c0t6d0 which simplifies typing, and saves space on command line in case
there are lots of disks. If there are 1 or 2 or 3 disks, you can simply skip the export D
command and type in the full dev files instead of $D/diskX syntax.
If all the above fails, the problem could be related to corruption regarding LVM in
memory so a reboot is necessary. This will become apparent when the VG activates
fine on node2, but fails on this node.
lvextend
1. PROBLEM lvextend: Error detected when reading from file "/etc/lvmpvg"