Print this page
11641 spelling mistakes in section 7d of the manual
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man7d/sd.7d.man.txt
+++ new/usr/src/man/man7d/sd.7d.man.txt
1 1 SD(7D) Devices SD(7D)
2 2
3 3
4 4
5 5 NAME
6 6 sd - SCSI disk and ATAPI/SCSI CD-ROM device driver
7 7
8 8 SYNOPSIS
9 9 sd@target,lun:partition
10 10
11 11
12 12 DESCRIPTION
13 13 To open a device without checking if the vtoc is valid, use the
14 14 O_NDELAY flag. When the device is opened using O_NDELAY, the first
15 15 read or write to the device that happens after the open results in the
16 16 label being read if the label is not currently valid. Once read, the
17 17 label remains valid until the last close of the device. Except for
18 18 reading the label, O_NDELAY has no impact on the driver.
19 19
20 20 SPARC
21 21 The sd SCSI and SCSI/ATAPI driver supports embedded SCSI-2 and
22 22 CCS-compatible SCSI disk and CD-ROM drives, ATAPI 2.6
23 23 (SFF-8020i)-compliant CD-ROM drives, SFF-8090-compliant SCSI/ATAPI DVD-
24 24 ROM drives, IOMEGA SCSI/ATAPI ZIP drives, SCSI JAZ drives, and USB mass
|
↓ open down ↓ |
24 lines elided |
↑ open up ↑ |
25 25 storage devices (refer to scsa2usb(7D)).
26 26
27 27
28 28 To determine the disk drive type, use the SCSI/ATAPI inquiry command
29 29 and read the volume label stored on block 0 of the drive. (The volume
30 30 label describes the disk geometry and partitioning and must be present
31 31 for the disk to be mounted by the system.) A volume label is not
32 32 required for removable, re-writable or read-only media.
33 33
34 34 x86 Only
35 - The sddriver supports embedded SCSI-2 and CCS-compatible SCSI disk and
35 + The sd driver supports embedded SCSI-2 and CCS-compatible SCSI disk and
36 36 CD-ROM drives, ATAPI 2.6 (SFF-8020i)-compliant CD-ROM drives,
37 37 SFF-8090-compliant SCSI/ATAPI DVD-ROM drives, IOMEGA SCSI/ATAPI ZIP
38 38 drives, and SCSI JAZ drives.
39 39
40 40
41 41 The x86 BIOS legacy requires a master boot record (MBR) and fdisk table
42 42 in the first physical sector of the bootable media. If the x86 hard
43 43 disk contains a Solaris disk label, it is located in the second
44 44 512-byte sector of the FDISK partition.
45 45
46 46 DEVICE SPECIAL FILES
47 47 Block-files access the disk using normal buffering mechanism and are
48 48 read-from and written-to without regard to physical disk records. A raw
49 49 interface enables direct transmission between the disk and the user's
50 50 read or write buffer. A single read or write call usually results in a
51 51 single I/O operation, therefore raw I/O is more efficient when many
52 52 bytes are transmitted. Block files names are found in /dev/dsk; raw
53 53 file names are found in /dev/rdsk.
54 54
55 55
56 56 I/O requests to the raw device must be aligned on a 512-byte
57 57 (DEV_BSIZE) boundary and all I/O request lengths must be in multiples
58 58 of 512 bytes. Requests that do not meet these requirements will
59 59 trigger an EINVAL error. There are no alignment or length restrictions
60 60 on I/O requests to the block device.
61 61
62 62 CD-ROM DRIVE SUPPORT
63 63 A CD-ROM disk is single-sided and contains approximately 640 megabytes
64 64 of data or 74 minutes of audio. When the CD-ROM is opened, the eject
65 65 button is disabled to prevent manual removal of the disk until the last
66 66 close() is called. No volume label is required for a CD-ROM. The disk
67 67 geometry and partitioning information are constant and never change. If
68 68 the CD-ROM contains data recorded in a Solaris-aware file system
69 69 format, it can be mounted using the appropriate Solaris file system
70 70 support.
71 71
72 72 DVD-ROM DRIVE SUPPORT
73 73 DVD-ROM media can be single or double-sided and can be recorded upon
74 74 using a single or double layer structure. Double-layer media provides
75 75 parallel or opposite track paths. A DVD-ROM can hold from between 4.5
76 76 Gbytes and 17 Gbytes of data, depending on the layer structure used for
77 77 recording and if the DVD-ROM is single or double-sided.
78 78
79 79
80 80 When the DVD-ROM is opened, the eject button is disabled to prevent the
81 81 manual removal of a disk until the last close() is called. No volume
82 82 label is required for a DVD-ROM. If the DVD-ROM contains data recorded
83 83 in a Solaris-aware file system format, it can be mounted using the
84 84 appropriate Solaris file system support.
85 85
86 86 ZIP/JAZ DRIVE SUPPORT
87 87 ZIP/JAZ media provide varied data capacity points; a single JAZ drive
88 88 can store up to 2 GBytes of data, while a ZIP-250 can store up to
89 89 250MBytes of data. ZIP/JAZ drives can be read-from or written-to using
90 90 the appropriate drive.
91 91
92 92
93 93 When a ZIP/JAZ drive is opened, the eject button is disabled to prevent
94 94 the manual removal of a disk until the last close() is called. No
95 95 volume label is required for a ZIP/JAZ drive. If the ZIP/JAZ drive
96 96 contains data recorded in a Solaris-aware file system format, it can be
97 97 mounted using the appropriate Solaris file system support.
98 98
99 99 DEVICE STATISTICS SUPPORT
|
↓ open down ↓ |
54 lines elided |
↑ open up ↑ |
100 100 Each device maintains I/O statistics for the device and for partitions
101 101 allocated for that device. For each device/partition, the driver
102 102 accumulates reads, writes, bytes read, and bytes written. The driver
103 103 also initiates hi-resolution time stamps at queue entry and exit points
104 104 to enable monitoring of residence time and cumulative residence-length
105 105 product for each queue.
106 106
107 107
108 108 Not all device drivers make per-partition IO statistics available for
109 109 reporting. sd and ssd(7D) per-partition statistics are enabled by
110 - default but may disabled in their configuration files.
110 + default but may be disabled in their configuration files.
111 111
112 112 IOCTLS
113 113 Refer to dkio(7I), and cdio(7I)
114 114
115 115 ERRORS
116 116 EACCES
117 117 Permission denied
118 118
119 119
120 120 EBUSY
121 121 The partition was opened exclusively by another thread
122 122
123 123
124 124 EFAULT
125 125 The argument features a bad address
126 126
127 127
128 128 EINVAL
129 129 Invalid argument
130 130
131 131
132 132 ENOTTY
133 133 The device does not support the requested ioctl function
134 134
135 135
136 136 ENXIO
137 137 During opening, the device did not exist. During close, the
138 138 drive unlock failed
139 139
140 140
141 141 EROFS
142 142 The device is read-only
143 143
144 144
145 145 EAGAIN
146 146 Resource temporarily unavailable
147 147
148 148
|
↓ open down ↓ |
28 lines elided |
↑ open up ↑ |
149 149 EINTR
150 150 A signal was caught during the execution of the ioctl()
151 151 function
152 152
153 153
154 154 ENOMEM
155 155 Insufficient memory
156 156
157 157
158 158 EPERM
159 - Insufficent access permission
159 + Insufficient access permission
160 160
161 161
162 162 EIO
163 163 An I/O error occurred. Refer to notes for details on copy-
164 164 protected DVD-ROM media.
165 165
166 166
167 167 CONFIGURATION
168 168 The sd driver can be configured by defining properties in the sd.conf
169 169 file. The sd driver supports the following properties:
170 170
171 171 enable-partition-kstats
172 172 The default value is 1, which causes
173 173 partition IO statistics to be maintained.
174 174 Set this value to zero to prevent the driver
175 175 from recording partition statistics. This
176 176 slightly reduces the CPU overhead for IO,
177 177 mimimizes the amount of sar(1) data
178 178 collected and makes these statistics
179 179 unavailable for reporting by iostat(1M) even
180 180 though the -p/-P option is specified.
181 181 Regardless of this setting, disk IO
182 182 statistics are always maintained.
183 183
184 184
185 185 qfull-retries
186 186 The supplied value is passed as the qfull-
187 187 retries capability value of the HBA driver.
188 188 See scsi_ifsetcap(9F) for details.
189 189
190 190
191 191 qfull-retry-interval
192 192 The supplied value is passed as the qfull-
193 193 retry interval capability value of the HBA
194 194 driver. See scsi_ifsetcap(9F) for details.
195 195
196 196
197 197 allow-bus-device-reset
198 198 The default value is 1, which allows
199 199 resetting to occur. Set this value to 0
200 200 (zero) to prevent the sd driver from calling
201 201 scsi_reset(9F) with a second argument of
202 202 RESET_TARGET when in error-recovery mode.
203 203 This scsi_reset(9F) call may prompt the HBA
204 204 driver to send a SCSI Bus Device Reset
205 205 message. The scsi_reset(9F) call with a
206 206 second argument of RESET_TARGET may result
207 207 from an explicit request via the USCSICMD
208 208 ioctl. Some high-availability multi-
209 209 initiator systems may wish to prohibit the
210 210 Bus Device Reset message; to do this, set
211 211 the allow-bus-device-reset property to 0.
212 212
213 213
214 214 optical-device-bind
215 215 Controls the binding of the driver to non
216 216 self-identifying SCSI target optical
217 217 devices. (See scsi(4)). The default value is
218 218 1, which causes sd to bind to DTYPE_OPTICAL
219 219 devices (as noted in scsi(4)). Setting this
220 220 value to 0 prevents automatic binding. The
221 221 default behavior for the SPARC-based sd
222 222 driver prior to Solaris 9 was not to bind to
223 223 optical devices.
224 224
225 225
226 226 power-condition
227 227 Boolean type, when set to False, it
228 228 indicates that the disk does not support
229 229 power condition field in the START STOP UNIT
230 230 command.
231 231
232 232
233 233
234 234 In addition to the above properties, some device-specific tunables can
235 235 be configured in sd.conf using the sd-config-list global property. The
236 236 value of this property is a list of duplets. The formal syntax is:
237 237
238 238 sd-config-list = <duplet> [, <duplet> ]* ;
239 239
240 240 where
241 241
242 242 <duplet>:= "<vid+pid>" , "<tunable-list>"
243 243
244 244 and
245 245
246 246 <tunable-list>:= <tunable> [, <tunable> ]*;
247 247 <tunable> = <name> : <value>
248 248
249 249 The <vid+pid> is the string that is returned by the target device
250 250 on a SCSI inquiry command.
251 251
252 252 The <tunable-list> contains one or more tunables to apply to
253 253 all target devices with the specified <vid+pid>.
254 254
255 255 Each <tunable> is a <name> : <value> pair. Supported
256 256 tunable names are:
257 257
258 258 delay-busy: when busy, nsecs of delay before retry.
259 259
260 260 retries-timeout: retries to perform on an IO timeout.
261 261
262 262
263 263 mmc-gesn-polling
264 264 For optical drives compliant with MMC-3 and
265 265 supporting the GET EVENT STATUS NOTIFICATION
266 266 command, this command is used for periodic media
267 267 state polling, usually initiated by the DKIOCSTATE
268 268 dkio(7I) ioctl. To disable the use of this command,
269 269 set this boolean property to false. In that case,
270 270 either the TEST UNIT READY or zero-length WRITE(10)
271 271 command is used instead.
272 272
273 273
274 274 EXAMPLES
275 275 The following is an example of a global sd-config-list property:
276 276
277 277 sd-config-list =
278 278 "SUN T4", "delay-busy:600, retries-timeout:6",
279 279 "SUN StorEdge_3510", "retries-timeout:3";
280 280
281 281
282 282 FILES
283 283 /kernel/drv/sd.conf
284 284 Driver configuration file
285 285
286 286
287 287 /dev/dsk/cntndnsn
288 288 Block files
289 289
290 290
291 291 /dev/rdsk/cntndnsn
292 292 Raw files
293 293
294 294
295 295
296 296 Where:
297 297
298 298 cn
299 299 controller n
300 300
301 301
302 302 tn
303 303 SCSI target id n (0-6)
304 304
305 305
306 306 dn
307 307 SCSI LUN n (0-7 normally; some HBAs support LUNs to 15 or 32. See
308 308 the specific manpage for details)
309 309
310 310
311 311 sn
312 312 partition n (0-7)
313 313
314 314
315 315 x86 Only
316 316 /dev/rdsk/cntndnpn
317 317 raw files
318 318
319 319
320 320
321 321 Where:
322 322
323 323 pn
324 324 Where n=0 the node corresponds to the entire disk.
325 325
326 326
327 327 SEE ALSO
328 328 sar(1), cfgadm_scsi(1M), fdisk(1M), format(1M), iostat(1M), close(2),
329 329 ioctl(2), lseek(2), read(2), write(2), driver.conf(4), scsi(4),
330 330 filesystem(5), scsa2usb(7D), ssd(7D), hsfs(7FS), pcfs(7FS), udfs(7FS),
331 331 cdio(7I), dkio(7I), scsi_ifsetcap(9F), scsi_reset(9F)
332 332
333 333
334 334 ANSI Small Computer System Interface-2 (SCSI-2)
335 335
336 336
337 337 ATA Packet Interface for CD-ROMs, SFF-8020i
338 338
339 339
340 340 Mt.Fuji Commands for CD and DVD, SFF8090v3
341 341
342 342 DIAGNOSTICS
343 343 Error for Command:<command name>
344 344 Error Level: Fatal
345 345 Requested Block: <n>
346 346 Error Block: <m>
347 347 Vendor:'<vendorname>'
348 348 Serial Number:'<serial number>'
349 349 Sense Key:<sense key name>
350 350
351 351
352 352
353 353 ASC: 0x<a> (<ASC name>), ASCQ: 0x<b>, FRU: 0x<c>
354 354
355 355 The command indicated by <command name> failed. The Requested Block
356 356 is the block where the transfer started and the Error Block is the
357 357 block that caused the error. Sense Key, ASC, and ASCQ information
358 358 is returned by the target in response to a request sense command.
359 359
360 360
361 361 Caddy not inserted in drive
362 362
363 363 The drive is not ready because no caddy has been inserted.
364 364
365 365
366 366 Check Condition on REQUEST SENSE
367 367
368 368 A REQUEST SENSE command completed with a check condition. The
369 369 original command will be retried a number of times.
370 370
371 371
372 372 Label says <m> blocks Drive says <n> blocks
373 373
374 374 There is a discrepancy between the label and what the drive
375 375 returned on the READ CAPACITY command.
376 376
377 377
378 378 Not enough sense information
379 379
380 380 The request sense data was less than expected.
381 381
382 382
383 383 Request Sense couldn't get sense data
384 384
385 385 The REQUEST SENSE command did not transfer any data.
386 386
387 387
388 388 Reservation Conflict
389 389
390 390 The drive was reserved by another initiator.
391 391
392 392
393 393 SCSI transport failed: reason 'xxxx': {retrying|giving up}
394 394
395 395 The host adapter has failed to transport a command to the target
396 396 for the reason stated. The driver will either retry the command or,
397 397 ultimately, give up.
398 398
399 399
400 400 Unhandled Sense Key<n>
401 401
402 402 The REQUEST SENSE data included an invalid sense.
403 403
404 404
405 405 Unit not ready. Additional sense code 0x
406 406
407 407 <n> The drive is not ready.
408 408
409 409
410 410 Can't do switch back to mode 1
411 411
412 412 A failure to switch back to read mode 1.
413 413
414 414
415 415 Corrupt label - bad geometry
416 416
417 417 The disk label is corrupted.
418 418
419 419
420 420 Corrupt label - label checksum failed
421 421
422 422 The disk label is corrupted.
423 423
424 424
425 425 Corrupt label - wrong magic number
426 426
427 427 The disk label is corrupted.
428 428
429 429
430 430 Device busy too long
431 431
432 432 The drive returned busy during a number of retries.
433 433
434 434
435 435 Disk not responding to selection
436 436
437 437 The drive is powered down or died
438 438
439 439
440 440 Failed to handle UA
441 441
442 442 A retry on a Unit Attention condition failed.
443 443
444 444
445 445 I/O to invalid geometry
446 446
447 447 The geometry of the drive could not be established.
448 448
449 449
450 450 Incomplete read/write - retrying/giving up
451 451
452 452 There was a residue after the command completed normally.
453 453
454 454
455 455 No bp for direct access device format geometry
456 456
457 457 A bp with consistent memory could not be allocated.
458 458
459 459
460 460 No bp for disk label
461 461
462 462 A bp with consistent memory could not be allocated.
463 463
464 464
465 465 No bp for fdisk
466 466
467 467 A bp with consistent memory could not be allocated.
468 468
469 469
470 470 No bp for rigid disk geometry
471 471
472 472 A bp with consistent memory could not be allocated.
473 473
474 474
475 475 No mem for property
476 476
477 477 Free memory pool exhausted.
478 478
479 479
480 480 No memory for direct access device format geometry
481 481
482 482 Free memory pool exhausted.
483 483
484 484
485 485 No memory for disk label
486 486
487 487 Free memory pool exhausted.
488 488
489 489
490 490 No memory for rigid disk geometry
491 491
492 492 The disk label is corrupted.
493 493
494 494
495 495 No resources for dumping
496 496
497 497 A packet could not be allocated during dumping.
498 498
499 499
500 500 Offline
501 501
502 502 Drive went offline; probably powered down.
503 503
504 504
505 505 Requeue of command fails
506 506
507 507 Driver attempted to retry a command and experienced a transport
508 508 error.
509 509
510 510
511 511 sdrestart transport failed()
512 512
513 513 Driver attempted to retry a command and experienced a transport
514 514 error.
515 515
516 516
517 517 Transfer length not modulo
518 518
519 519 Illegal request size.
520 520
521 521
522 522 Transport of request sense fails()
523 523
524 524 Driver attempted to submit a request sense command and failed.
525 525
526 526
527 527 Transport rejected()
528 528
529 529 Host adapter driver was unable to accept a command.
530 530
531 531
532 532 Unable to read label
533 533
534 534 Failure to read disk label.
535 535
536 536
537 537 Unit does not respond to selection
538 538
539 539 Drive went offline; probably powered down.
540 540
|
↓ open down ↓ |
371 lines elided |
↑ open up ↑ |
541 541
542 542 NOTES
543 543 DVD-ROM media containing DVD-Video data may follow/adhere to the
544 544 requirements of content scrambling system or copy protection scheme.
545 545 Reading of copy-protected sector will cause I/O error. Users are
546 546 advised to use the appropriate playback software to view video contents
547 547 on DVD-ROM media containing DVD-Video data.
548 548
549 549
550 550
551 - May 13, 2017 SD(7D)
551 + January 10, 2020 SD(7D)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX