VERITAS Volume Manager 3.5 Administrator's Guide (September 2002)

Changing the Disk-Naming Scheme

62 VERITAS Volume Manager Administrator’s Guide

Using vxprint with Enclosure-Based Disk Names

If you enable enclosure-based naming, and use the vxprint command to display the

structure of a volume, it shows enclosure-based disk device names (disk access names)

rather than c#t#d names. To discover the c#t#d names that are associated with a given

enclosure-based disk name, use either of the following commands:

# vxdisk list enclosure-based_name

# vxdmpadm getsubpaths dmpnodename=enlcosure-based_name

For example, to ﬁnd 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 obtainthe full pathname forthe blockand character disk devicefrom these commands,

append the displayed device name to /dev/dsk or /dev/rdsk.

Issues Regarding Persistent Simple/Nopriv Disks with

Enclosure-Based Naming

If you change from the c#t#d# based naming scheme to the enclosure-based naming

scheme, persistent simple or nopriv disks may be put in the “error” state and cause

VxVM objects on those disks to fail. If this happens, use the following procedures to

correct the problem:

◆ Persistent Simple/Nopriv Disks in the Root Disk Group

◆ Persistent Simple/Nopriv Disks in Non-Root Disk Groups

These procedures use the vxdarestore utility to handle errors in persistent simple and

nopriv disks that arise from changing to the enclosure-based naming scheme. You do not

need to perform either procedure if the devices on which any simple or nopriv disks are

present are not automatically conﬁgured by VxVM (for example, non-standard disk

devices such as ramdisks).

Note The disk access records for simple disks are either persistent or non-persistent. The

disk access record for a persistent simple disk is stored in the disk’s private region.

The disk access record for a non-persistent simple disk is automatically conﬁgured

in memory at VxVM startup. A simple disk has a non-persistent disk access record

if autoconfig is included in the flags ﬁeld that is displayed by the vxdisk

list disk_access_name command. If the autoconfig ﬂag is not present, the disk

access record is persistent. Nopriv disks are always persistent.