Symantec logo

Persistent simple or nopriv disks with enclosure-based naming

If you change from OS-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.

You can use the vxdarestore command 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 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 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.


See "Removing the error state for persistent simple or nopriv disks in the boot disk group" on page 96.

See "Removing the error state for persistent simple or nopriv disks in non-boot disk groups" on page 97.

See the vxdarestore(1M) manual page.

Removing the error state for persistent simple or nopriv disks in the boot disk group

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.


  Note   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.


 To remove the error state for persistent simple or nopriv disks in the boot disk group

  1. Use vxdiskadm to change back to c#t#d# naming.
  2. Enter the following command to restart the VxVM configuration daemon:

    # vxconfigd -kr reset

  3. If you want to use enclosure-based naming, use vxdiskadm to add a non-persistent simple disk to the bootdg disk group, change back to the enclosure-based naming scheme, and then run the following command:

    # /etc/vx/bin/vxdarestore

Removing the error state for persistent simple or nopriv disks in non-boot disk groups

If an imported disk group, other than bootdg, consists only of persistent simple and/or nopriv disks, it is put in the "online 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

  1. Deport the disk group using the following command:

    # vxdg deport diskgroup

  2. Use the vxdarestore command to restore the failed disks, and to recover the objects on those disks:

    # /etc/vx/bin/vxdarestore

  3. Re-import the disk group using the following command:

    # vxdg import diskgroup