Administering disks

Changing the disk-naming scheme

#vxdmpadm getlungroup dmpnodename=disk25

VxVM vxdmpadm ERROR V-5-1-10910 Invalid da-name

#vxdmpadm getlungroup dmpnodename=Disk_11

NAME STATE ENCLR-TYPE PATHS ENBL DSBL ENCLR-NAME

===============================================================

Disk_11 ENABLED Disk

2

2

0

Disk

To find out which sort of naming is currently enabled, use the vxddladm get namingscheme command, as shown in the following example:

#vxddladm get namingscheme

NAMING_SCHEME PERSISTENCE MODE

===============================================

OS Native

Yes

New

The effect of enabling persistent device names in conjunction with operating system-based naming is discussed in “Regenerating persistent device names” on page 93.

93

Regenerating persistent device names

The persistent device naming feature makes the DDL-assigned 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

To update the disk names so that they correspond to the new path names

1Remove the file that contains the existing persistent device name database:

#rm /etc/vx/disk.info

2Restart the VxVM configuration demon:

#vxconfigd -k

This regenerates the persistent name database.

Page 92
Image 92
HP Veritas Volume Manager 5.0 -UX 11i v3 manual Regenerating persistent device names, Restart the VxVM configuration demon