NAME | SYNOPSIS | DESCRIPTION | IOCTLS | ERRORS | FILES | SEE ALSO | DIAGNOSTICS
ssd@port,target:partition
This driver handles both SCSI-2 disks in the SPARCstorage Array and Fibre Channel Arbitrated Loop (FC-AL) disks on Private loops.
The specific type of each disk is determined by the SCSI inquiry command and reading the volume label stored on block 0 of the drive. The volume label describes the disk geometry and partitioning; it must be present or the disk cannot be mounted by the system.
The block-files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are transmitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk.
I/O requests (such as lseek(2)) to the SCSI disk must have an offset that is a multiple of 512 bytes (DEV_BSIZE), or the driver returns an EINVAL error. If the transfer length is not a multiple of 512 bytes, the transfer count is rounded up by the driver.
Partition 0 is normally used for the root file system on a disk, partition 1 as a paging area (for example, swap), and partition 2 for backing up the entire disk. Partition 2 normally maps the entire disk and may also be used as the mount point for secondary disks in the system. The rest of the disk is normally partition 6. For the primary disk, the user file system is located here.
Each device also has error statistics associated with it. These must include counters for hard errors, soft errors and transport errors. Other data may be implemented as required.
Refer to dkio(7I).
Permission denied.
The partition was opened exclusively by another thread.
The argument was a bad address.
Invalid argument.
An I/O error occurred.
The device does not support the requested ioctl function.
When returned during open(2), this error indicates the device does not exist.
The device is a read-only device.
driver configuration file
block files
raw files
where, for the SPARCstorage Array:
is the controller number on the system. Each SPARCstorage Array will have a unique controller number
port number within the SPARCstorage Array n
SCSI target n
partition n
and for all FC-AL disks:
is the controller number on the system.
7-bit disk loop identifier, such as switch setting
SCSI lun n
partition n (0-7)
format(1M), ioctl(2), lseek(2), open(2), read(2), write(2), driver.conf(4), cdio(7I), dkio(7I)
ANSI Small Computer System Interface-2 (SCSI-2) SPARCstorage Array User's Guide ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL) Fibre Channel - Private Loop SCSI Direct Attach (FC-PLDA)
Error for command '<command name>' Error Level: Fatal Requested Block <n>, Error Block: <m> Sense Key: <sense key name> Vendor '<vendor name>': ASC = 0x<a> (<ASC name>), ASCQ = 0x<b>, FRU = 0x<c>The command indicated by <command name> failed. The Requested Block is the block where the transfer started and the Error Block is the block that caused the error. Sense Key, ASC, and ASCQ information is returned by the target in response to a request sense command.
A REQUEST SENSE command completed with a check condition. The original command will be retried a number of times.
There is a discrepancy between the label and what the drive returned on the READ CAPACITY command.
The request sense data was less than expected.
The REQUEST SENSE command did not transfer any data.
The drive was reserved by another initiator.
The host adapter has failed to transport a command to the target for the reason stated. The driver will either retry the command or, ultimately, give up.
The REQUEST SENSE data included an invalid sense key.
The drive is not ready.
The disk label is corrupted.
The disk label is corrupted.
The disk label is corrupted.
The drive returned busy during a number of retries.
The drive was probably powered down or died.
The geometry of the drive could not be established.
There was a residue after the command completed normally.
The drive is not ready.
A bp with consistent memory could not be allocated.
Free memory pool exhausted.
Free memory pool exhausted.
A packet could not be allocated during dumping.
Drive went offline; probably powered down.
Driver attempted to retry a command and experienced a transport error.
Driver attempted to retry a command and experienced a transport error.
Illegal request size.
Host adapter driver was unable to accept a command.
Failure to read disk label.
Drive went offline; probably powered down.
NAME | SYNOPSIS | DESCRIPTION | IOCTLS | ERRORS | FILES | SEE ALSO | DIAGNOSTICS