1ssd(7D) Devices ssd(7D)
2
6 ssd - Fibre Channel Arbitrated Loop disk device driver
7
9 ssd@port,target:partition
10
13 The ssd driver supports Fibre Channel disk devices.
14 The specific type of each disk is determined by the SCSI inquiry com‐
17 mand and reading the volume label stored on block 0 of the drive. The
18 volume label describes the disk geometry and partitioning; it must be
19 present or the disk cannot be mounted by the system.
20 The block-files access the disk using the system's normal buffering
23 mechanism and are read and written without regard to physical disk
24 records. A "raw" interface provides for direct transmission between the
25 disk and the read or write buffer. A single read or write call usually
26 results in one I/O operation; raw I/O is therefore more efficient when
27 many bytes are transmitted. Block file names are found in /dev/dsk; the
28 names of the raw files are found in /dev/rdsk.
29 I/O requests (such as lseek(2)) to the SCSI disk must have an offset
32 that is a multiple of 512 bytes (DEV_BSIZE), or the driver returns an
33 EINVAL error. If the transfer length is not a multiple of 512 bytes,
34 the transfer count is rounded up by the driver.
35 Partition 0 is normally used for the root file system on a disk, with
38 partition 1 as a paging area (for example, swap). Partition 2 is used
39 to back up the entire disk. Partition 2 normally maps the entire disk
40 and may also be used as the mount point for secondary disks in the sys‐
41 tem. The rest of the disk is normally partition 6. For the primary
42 disk, the user file system is located here.
43 The device has associated error statistics. These must include counters
46 for hard errors, soft errors and transport errors. Other data may be
47 implemented as required.
48
50 The device maintains I/O statistics for the device and for partitions
51 allocated for that device. For each device/partition, the driver accu‐
52 mulates reads, writes, bytes read, and bytes written. The driver also
53 initiates hi-resolution time stamps at queue entry and exit points to
54 enable monitoring of residence time and cumulative residence-length
55 product for each queue.
56 Not all device drivers make per-partition IO statistics available for
59 reporting. ssd and sd(7D) per-partition statistics are enabled by
60 default but may be disabled in their configuration files.
61
63 Refer to dkio(7I).
64
66 EACCES Permission denied.
67 EBUSY The partition was opened exclusively by another thread.
70 EFAULT The argument was a bad address.
73 EINVAL Invalid argument.
76 EIO An I/O error occurred.
79 ENOTTY The device does not support the requested ioctl function.
82 ENXIO When returned during open(2), this error indicates the
85 device does not exist.
86 EROFS The device is a read-only device.
89
92 You configure the ssd driver by defining properties in the ssd.conf
93 file. The ssd driver supports the following properties:
94 enable-partition-kstats The default value is 1, which causes parti‐
96 tion IO statistics to be maintained. Set
97 this value to zero to prevent the driver
98 from recording partition statistics. This
99 slightly reduces the CPU overhead for IO,
100 mimimizes the amount of sar(1) data col‐
101 lected and makes these statistics unavail‐
102 able for reporting by iostat(1M) even though
103 the -p/-P option is specified. Regardless
104 of this setting, disk IO statistics are
105 always maintained.
106 In addition to the above properties, some device-specific tunables can
110 be configured in ssd.conf using the 'ssd-config-list' global property.
111 The value of this property is a list of duplets. The formal syntax is:
112 ssd-config-list = <duplet> [, <duplet> ]* ;
114 where
116 <duplet>:= "<vid+pid>" , "<tunable-list>"
118 and
120 <tunable-list>:= <tunable> [, <tunable> ]*;
122 <tunable> = <name> : <value>
123 The <vid+pid> is the string that is returned by the target device
125 on a SCSI inquiry command.
126 The <tunable-list> contains one or more tunables to apply to
128 all target devices with the specified <vid+pid>.
129 Each <tunable> is a <name> : <value> pair. Supported
131 tunable names are:
132 delay-busy: when busy, nsecs of delay before retry.
134 retries-timeout: retries to perform on an IO timeout.
136
139 The following is an example of a global ssd-config-list property:
140 ssd-config-list =
142 "SUN T4", "delay-busy:600, retries-timeout:6",
143 "SUN StorEdge_3510", "retries-timeout:3";
144
147 ssd.conf Driver configuration file
148 /dev/dsk/cntndnsn block files
151 /dev/rdsk/cntndnsn raw files
154 cn is the controller number on the system.
157 tn 7-bit disk loop identifier, such as switch set‐
160 ting
161 dn SCSI lun n
164 sn partition n (0-7)
167
170 sar(1), format(1M), iostat(1M), ioctl(2), lseek(2), open(2), read(2),
171 write(2), scsi(4)driver.conf(4), cdio(7I), dkio(7I)
172 ANSI Small Computer System Interface-2 (SCSI-2)
175 ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
178 Fibre Channel - Private Loop SCSI Direct Attach (FC-PLDA)
181
183 Error for command '<command name>' Error Level: Fatal Requested Block <n>,
184 Error Block: <m>, Sense Key: <sense key name>, Vendor '<vendor name>':
185 ASC = 0x<a> (<ASC name>), ASCQ = 0x<b>, FRU = 0x<c>
186 The command indicated by <command name> failed. The Requested Block is
191 the block where the transfer started and the Error Block is the block
192 that caused the error. Sense Key, ASC, and ASCQ information is returned
193 by the target in response to a request sense command.
194 Check Condition on REQUEST SENSE
196 A REQUEST SENSE command completed with a check condition. The original
201 command will be retried a number of times.
202 Label says <m> blocks Drive says <n> blocks
204 There is a discrepancy between the label and what the drive returned on
209 the READ CAPACITY command.
210 Not enough sense information
212 The request sense data was less than expected.
217 Request Sense couldn't get sense data
219 The REQUEST SENSE command did not transfer any data.
224 Reservation Conflict
226 The drive was reserved by another initiator.
231 SCSI transport failed: reason 'xxxx' : {retrying|giving up}
233 The host adapter has failed to transport a command to the target for
238 the reason stated. The driver will either retry the command or, ulti‐
239 mately, give up.
240 Unhandled Sense Key <n>
242 The REQUEST SENSE data included an invalid sense key.
247 Unit not Ready. Additional sense code 0x<n>
249 The drive is not ready.
254 corrupt label - bad geometry
256 The disk label is corrupted.
261 corrupt label - label checksum failed
263 The disk label is corrupted.
268 corrupt label - wrong magic number
270 The disk label is corrupted.
275 device busy too long
277 The drive returned busy during a number of retries.
282 disk not responding to selection
284 The drive was probably powered down or died.
289 i/o to invalid geometry
291 The geometry of the drive could not be established.
296 incomplete read/write - retrying/giving up
298 There was a residue after the command completed normally.
303 logical unit not ready
305 The drive is not ready.
310 no bp for disk label
312 A bp with consistent memory could not be allocated.
317 no mem for property
319 Free memory pool exhausted.
324 no memory for disk label
326 Free memory pool exhausted.
331 no resources for dumping
333 A packet could not be allocated during dumping.
338 offline
340 Drive went offline; probably powered down.
345 requeue of command fails<n>
347 Driver attempted to retry a command and experienced a transport error.
352 ssdrestart transport failed <n>
354 Driver attempted to retry a command and experienced a transport error.
359 transfer length not modulo <n>
361 Illegal request size.
366 transport rejected <n>
368 Host adapter driver was unable to accept a command.
373 unable to read label
375 Failure to read disk label.
380 unit does not respond to selection
382 Drive went offline; probably powered down.
387SunOS 5.11 9 Aug 2008 ssd(7D)