VERITAS Volume Manager 4.1 Administrator's Guide

Chapter 2 80
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 80
• “Persistent Simple/Nopriv Disks in Non-Root Disk Groups” on page 81
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 configured 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
configured in memory at VxVM startup. A simple disk has a non-persistent
disk access record if autoconfig is included in the flags field that is displayed by
the vxdisk list disk_access_name command. If the autoconfig flag 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 reconfiguration
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.
Persistent Simple/Nopriv Disks in the Root Disk Group
If all persistent simple and nopriv disks in rootdg go into the error state and the vxconfigd
daemon is disabled after the naming scheme change, perform the following steps:
Step 1. Use vxdiskadm to change back to the c#t#d# naming scheme.
Step 2. Either shut down and reboot the system, or enter the following command to restart
the VxVM configuration daemon:
# vxconfigd -kr reset