Veritas Volume Manager 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)

Changing the Disk-Naming Scheme
74 VERITAS Volume Manager Administrator’s Guide
For example, to find the physical device that is associated with disk ENC0_21, the
appropriate commands would be:
# vxdisk list ENC0_21
# vxdmpadm getsubpaths dmpnodename=ENC0_21
To obtain the full pathname for the block and character disk device from these commands,
append the displayed device name to /dev/dsk or /dev/rdsk.
Regenerating the Persistent Device Name Database
The persistent device naming feature, introduced in VxVM 4.1, makes the names of disk
devices persistent across system reboots. If operating system-based naming is selected,
each disk name is usually set to the name of one of the paths to the disk. After hardware
reconfiguration and a subsequent reboot, the operating system may generate different
names for the paths to the disks. As DDL assigns persistent disk names using the
persistent device name database that was generated during a previous boot session, the
disk names may no longer correspond to the actual paths. This does not prevent the disks
from being used, but the association between the disk name and one of its paths is lost.
To find the relationship between a disk and its paths, run one of the following commands:
# vxdmpadm getsubpaths dmpnodename=disk_access_name
# vxdisk list disk_access_name
If you want to update the disk names so that they correspond to the new path names,
perform the following steps:
1. Remove the file that contains the existing persistent device name database:
# rm /etc/vx/disk.info
2. Restart the VxVM configuration demon:
# vxconfigd -k
This regenerates the persistent name database.