VERITAS Volume Manager 3.5 Administrator's Guide (September 2002)

Chapter 2, Administering Disks

Changing the Disk-Naming Scheme

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 reconﬁguration 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:

1. Use vxdiskadm to change back to the c#t#d# naming scheme.

2. Either shut down and reboot the system, or enter the following command to restart

the VxVM conﬁguration daemon:

# vxconfigd -kr reset

3. If you want to use the enclosure-based naming scheme, use vxdiskadm to add a

non-persistent simple disk to the rootdg disk group, change back to the

enclosure-based naming scheme, and then run the following command:

# /usr/bin/vxvm/bin/vxdarestore

Note If not all the disks in rootdg 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.

Persistent Simple/Nopriv Disks in Non-Root Disk Groups

If an imported disk group other than rootdg, consisting only of persistent simple and/or

nopriv disks, is put in the “online dgdisabled” state after the change to the

enclosure-based naming scheme, perform the following steps:

1. Deport the disk group using the following command:

# vxdg deport diskgroup

2. Use the vxdarestore command torestore the failed disks, and to recoverthe objects

on those disks: