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

Chapter 2 67
NOTE The s2 component of the device name is required to specify the HP-UX
partition of an EFI formatted physical disk that is sued to boot an HP
Itanium 2 based system. The root disk on an HP IPF system is divided
into partitions where the c#t#d# device contains the EFI header
information, c#t#d#s1 is an EFI file system that contains the Itanium
boot loader, and c#t#d#s2 is an HP-UX partition. The c#t#d#s2 device
may be accessed in the same way as the c#t#d# devices for disks that are
not EFI formatted (all such disks are accessed by specifying the c#t#d#
form of the device name, which should not include the s2 component).
Fabric mode disk devices are named as follows:
• Disk in supported disk arrays are named using the enclosure
name_# format. For example, disks in the supported disk array name
FirstFloor are named FirstFloor_0, FirstFloor_1, FirstFloor_2 and so
on. (You can use the vxdmpadm command to administer enclosure
names.)
• Disks in the DISKS category (formerly know as JBOD disks) are
named using the Disk_# format.
• Disks in the OTHER_DISKS category are named using the fabric_#
format
Enclosure Based Naming Scheme
The enclosure-based naming scheme operates as follows:
• All fabric or non-fabric disks in supported disk arrays are named
using the enclosure_name_# format. For example, disks in the
supported disk array, enggdept are named enggdept_0, enggdept_1,
enggdept_2 and so on. (You can use the vxdmpadm command to
administer enclosure names. See “Administering DMP Using
vxdmpadm” on page 124 and the vxdmpadm(1M) manual page for
more information.)
• Disks in the DISKS category (formerly known as JBOD disks) are
named using the Disk_# format.
• Disks in the OTHER_DISKS category are named as follows: