You can either
use enclosure-based naming for disks or the traditional naming scheme
(such as c#t#d#). Select menu item 20 from the vxdiskadm
main menu to change the disk-naming scheme that you want VxVM to
use. Selecting this option displays the following screen:
Change the disk naming scheme
Menu: VolumeManager/Disk/NamingScheme
Use this screen to change the disk naming scheme (from the c#t#d# format to the enclosure based format and vice versa).
NOTE: This operation will result in vxconfigd being stopped and restarted.
Do you want to change the naming scheme ? [y,n,q,?] (default: n) |
Enter y to change the naming scheme. This restarts the vxconfig
daemon to bring the new disk naming scheme into effect.
Using
vxprint with Enclosure-Based Disk Names |
 |
If
you enable enclosure-based naming, and use the vxprint command to display
the structure of a volume, it shows enclosure-based disk device names
(disk access names) rather than c#t#d names. To discover the c#t#d
names that are associated with a given enclosure-based disk name, use
either of the following commands:
# vxdisk list enclosure-based_name
# vxdmpadm getsubpaths dmpnodename=enlcosure-based_name
For example, to find the physical device that is associated
with disk ENC0_21, the appropriate commands would be:
# vxdisk list ENC0_21
# vxdmpadm getsubpaths dmpnodename=ENC0_21
To obtain the full pathname for the block and character disk
device from these commands, append the displayed device name to
.
Issues
Regarding Persistent Simple/Nopriv Disks with Enclosure-Based Naming |
|
If you
change from the c#t#d# based naming scheme to the enclosure-based
naming scheme, 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).
|
| |
|
 | NOTE: 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.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 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.
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:
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:
Deport the disk group using the following
command:
# vxdg deport diskgroup
Use the vxdarestore command to restore the failed disks,
and to recover the objects on those disks:
# /usr/bin/vxvm/bin/vxdarestore
Re-import the disk group using the following command:
# vxdg import diskgroup
Printable version
