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

Chapter 2 77

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” on page 78

• “Persistent Simple/Nopriv Disks in Non-Root Disk Groups” on

page 78

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

autoconﬁg is included in the ﬂags ﬁeld that is displayed by the vxdisk list

disk_access_name command. If the autoconﬁg ﬂag is not present, the

disk access record is persistent. Nopriv disks are always persistent.

NOTE You cannot run vxdarestore if the c#t#d# naming scheme is in use.

Additionally, vxdarestore does not handle failures on persistent

simple/nopriv disks that are caused by renaming enclosures, by

hardware reconﬁguration that changes device names. or by removing

support from the JBOD category for disks that belong to a particular

vendor when enclosure-based naming is in use.

For more information about the vxdarestore command, see the

vxdarestore(1M) manual page.