If you change from c#t#d# based naming to enclosure-based naming, 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:
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).
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
list disk_access_name command. If the
autoconfig flag is not present, the disk access record is persistent. Nopriv disks are always persistent.
You cannot run
vxdarestore if c#t#d# naming 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.
If all persistent simple and nopriv disks in the boot disk group (usually aliased as
bootdg) go into the error state, the
vxconfigd daemon is disabled after the naming scheme change.
To remove the error state for persistent simple or nopriv disks in the boot disk group
vxconfigd -kr reset
vxdiskadmto add a non-persistent simple disk to the
bootdgdisk group, change back to the enclosure-based naming scheme, and then run the following command:
If not all the disks in
bootdg go into the error state, you need only run
vxdarestore to restore the disks that are in the error state and the objects that they contain.
If an imported disk group, other than
bootdg, consists only of persistent simple and/or nopriv disks, it is put in the "
dgdisabled" state after the change to the enclosure-based naming scheme.
To remove the error state for persistent simple or nopriv disks in non-boot disk groups
vxdg deport diskgroup
vxdarestorecommand to restore the failed disks, and to recover the objects on those disks:
vxdg import diskgroup