System Administration Guide: Devices and File Systems

Logical Disk Device Names

Logical device names are used to access disk devices when you:

Many administration commands take arguments that refer to a disk slice or file system.

Refer to a disk device by specifying the subdirectory to which it is symbolically linked, either /dev/dsk or /dev/rdsk, followed by a string identifying the particular controller, disk, and slice.

Figure 9–1 Logical Device Names

Diagram of logical device name components: raw disk device
directory, logical controller, physical bus target, drive, and slice or fdisk
partition.

Specifying the Disk Subdirectory

Disk and file administration commands require the use of either a raw (or character) device interface, or a block device interface. The distinction is made by how data is read from the device.

Raw device interfaces transfer only small amounts of data at a time. Block device interfaces include a buffer from which large blocks of data are read at once.

Different commands require different interfaces.

The following table shows which interface is required for some commonly used disk and file system commands.

Table 9–1 Device Interface Type Required by Some Frequently Used Commands

Command 

Interface Type 

Example of Use 

df(1M)

Block 

df /dev/dsk/c0t3d0s6

fsck(1M)

Raw 

fsck -p /dev/rdsk/c0t0d0s0

mount(1M)

Block 

mount /dev/dsk/c1t0d0s7 /export/home

newfs(1M)

Raw 

newfs /dev/rdsk/c0t0d1s1

prtvtoc(1M)

Raw 

prtvtoc /dev/rdsk/c0t0d0s2

Specifying the Slice

The string that you use to identify a specific slice on a specific disk depends on the controller type, either direct or bus-oriented. The following table describes the different types of direct or bus-oriented controllers on different platforms.

Table 9–2 Controller Types

Direct controllers 

Bus-Oriented Controllers 

IDE (x86) 

SCSI (SPARC/x86) 

 

FCAL (SPARC) 

 

ATA (SPARC/x86) 

The conventions for both types of controllers are explained in the following subsections.


Note –

Controller numbers are assigned automatically at system initialization. The numbers are strictly logical and imply no direct mapping to physical controllers.


x86: Disks With Direct Controllers

To specify a slice on a disk with an IDE controller on an x86 based system, follow the naming convention shown in the following figure.

Figure 9–2 x86: Disks with Direct Controllers

Diagram of device name for disks with direct controllers
that includes logical controller, drive, and slice or fdisk partition.

To indicate the entire Solaris fdisk partition, specify slice 2 (s2).

If you have only one controller on your system, w is usually 0.

SPARC: Disks With Bus-Oriented Controllers

To specify a slice on a disk with a bus-oriented controller, SCSI for instance, on a SPARC based system, follow the naming convention shown in the following figure.

Figure 9–3 SPARC: Disks With Bus-Oriented Controllers

Device name for disks with bus-oriented controllers that
includes logical controller, physical bus target, drive, and slice or fdisk
partition.

On a SPARC based system with directly connected disks such as the IDE disks on a Ultra10, the naming convention is the same as that for systems with bus-oriented controllers.

If you have only one controller on your system, w is usually 0.

For SCSI controllers, x is the target address set by the switch on the back of the unit, and y is the logical unit number (LUN) of the drive attached to the target. If the disk has an embedded controller, y is usually 0.

To indicate the whole disk, specify slice 2 (s2).

x86: Disks With SCSI Controllers

To specify a slice on a disk with a SCSI controller on an x86 based system, follow the naming convention shown in the following figure.

Figure 9–4 x86: Disks with SCSI Controllers

Device name for disks with bus-oriented controllers that
includes logical controller, physical bus target, drive, and slice or fdisk
partition.

If you have only one controller on your system, v is usually 0.

For SCSI controllers, w is the target address set by the switch on the back of the unit, and x is the logical unit number (LUN) of the drive attached to the target. If the disk has an embedded controller, x is usually 0.

To indicate the entire Solaris fdisk partition, specify slice 2 (s2).