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

HP-UX Handbook – Rev 13.00 Page 89 (of 110)
Chapter 13 LVM
October 29, 2013
# ll /dev/dsk/c15*
/dev/dsk/c15* not found
RESOLUTION
The reason for that is that the instance numbers have changed.
They have changed because the system was booted from the boot disk of another
system which was supposed to be identical in HW (this is a common "HA" solution
bypassing the need of professional cluster software like MC/ServiceGuard,
usually used with boot disk on fibre channel devices).
As a result the devicefiles for the disks changed.
The system is still accessing the PVs through their old devicefiles,
VGs could be activated, FS coud be mounted, applications could run.
But HW scanning commands like vgscsan fail under such circumstances.
The solution is to use insf(1M) to rename the devicefiles according the given
the ext_bus instance numbers and to recreate lvmtab using vgscan to include the
new devicefiles.
# insf -e
...
# vgscan -v
...
# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/vg02
/dev/dsk/c14t5d0 <<< new
/dev/dsk/c15t5d0 <<< new
/dev/vg01
/dev/dsk/c14t6d0 <<< new
/dev/dsk/c15t6d0 <<< new
what changed? c4t*d* --> c14t*d* and
c6t*d* --> c15t*d*
If there is any application that has the names of disk devicefiles hard coded
in it's configuration you need to change it accordingly.
2.PROBLEM - vgscan: unable to match physical volume to a volume group