< Previous  | TOC | Index | Next  >

Simple or nopriv disks with enclosure-based naming

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

You can use the vxdarestore command to handle simple/nopriv disk failures that arise from changing to the enclosure-based naming scheme. You do not need to use this command 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 OS-based 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.

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

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

See the vxdarestore(1M) manual page.

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

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

1. Use vxdiskadm to change back to c#t#d#s# 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 sliced 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 simple or nopriv disks in non-boot disk groups

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

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