|
|
|
|
|
If you change from c#t#d#s# based naming to enclosure-based naming, 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 simple/nopriv disk failures that arise from changing to the enclosure-based naming scheme. You do not need to perform either procedure if your system does not have any simple or nopriv disks, or 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
You cannot run vxdarestore if c#t#d#s# naming is in use. Additionally, vxdarestore does not handle failures on simple/nopriv disks that are caused by renaming enclosures, by hardware reconfiguration that changes device names, or by changing the naming scheme on a system that includes persistent sliced disk records.
For more information about the vxdarestore command, see the vxdarestore(1M) manual page.
If the boot disk group (usually aliased as bootdg) is comprised of only simple and/or nopriv disks, the vxconfigd daemon goes into the disabled state after the naming scheme change.
To remove the error state for simple or nopriv disks in the boot disk group
vxdiskadm to change back to c#t#d#s# naming.
vxdiskadm to add a sliced disk to the bootdg disk group, change back to the enclosure-based naming scheme, and then run the following command:
If an imported disk group, other than bootdg, is comprised of only simple and/or nopriv disks, the disk group is in the "online dgdisabled" state after the change to the enclosure-based naming scheme.
To remove the error state for simple or nopriv disks in non-boot disk groups
vxdarestore command to restore the failed disks, and to recover the objects on those disks: