15 read or write to the device that happens after the open results in the
16 label being read if the label is not currently valid. Once read, the
17 label remains valid until the last close of the device. Except for
18 reading the label, O_NDELAY has no impact on the driver.
19
20 SPARC
21 The sd SCSI and SCSI/ATAPI driver supports embedded SCSI-2 and
22 CCS-compatible SCSI disk and CD-ROM drives, ATAPI 2.6
23 (SFF-8020i)-compliant CD-ROM drives, SFF-8090-compliant SCSI/ATAPI DVD-
24 ROM drives, IOMEGA SCSI/ATAPI ZIP drives, SCSI JAZ drives, and USB mass
25 storage devices (refer to scsa2usb(7D)).
26
27
28 To determine the disk drive type, use the SCSI/ATAPI inquiry command
29 and read the volume label stored on block 0 of the drive. (The volume
30 label describes the disk geometry and partitioning and must be present
31 for the disk to be mounted by the system.) A volume label is not
32 required for removable, re-writable or read-only media.
33
34 x86 Only
35 The sddriver supports embedded SCSI-2 and CCS-compatible SCSI disk and
36 CD-ROM drives, ATAPI 2.6 (SFF-8020i)-compliant CD-ROM drives,
37 SFF-8090-compliant SCSI/ATAPI DVD-ROM drives, IOMEGA SCSI/ATAPI ZIP
38 drives, and SCSI JAZ drives.
39
40
41 The x86 BIOS legacy requires a master boot record (MBR) and fdisk table
42 in the first physical sector of the bootable media. If the x86 hard
43 disk contains a Solaris disk label, it is located in the second
44 512-byte sector of the FDISK partition.
45
46 DEVICE SPECIAL FILES
47 Block-files access the disk using normal buffering mechanism and are
48 read-from and written-to without regard to physical disk records. A raw
49 interface enables direct transmission between the disk and the user's
50 read or write buffer. A single read or write call usually results in a
51 single I/O operation, therefore raw I/O is more efficient when many
52 bytes are transmitted. Block files names are found in /dev/dsk; raw
53 file names are found in /dev/rdsk.
54
55
90 the appropriate drive.
91
92
93 When a ZIP/JAZ drive is opened, the eject button is disabled to prevent
94 the manual removal of a disk until the last close() is called. No
95 volume label is required for a ZIP/JAZ drive. If the ZIP/JAZ drive
96 contains data recorded in a Solaris-aware file system format, it can be
97 mounted using the appropriate Solaris file system support.
98
99 DEVICE STATISTICS SUPPORT
100 Each device maintains I/O statistics for the device and for partitions
101 allocated for that device. For each device/partition, the driver
102 accumulates reads, writes, bytes read, and bytes written. The driver
103 also initiates hi-resolution time stamps at queue entry and exit points
104 to enable monitoring of residence time and cumulative residence-length
105 product for each queue.
106
107
108 Not all device drivers make per-partition IO statistics available for
109 reporting. sd and ssd(7D) per-partition statistics are enabled by
110 default but may disabled in their configuration files.
111
112 IOCTLS
113 Refer to dkio(7I), and cdio(7I)
114
115 ERRORS
116 EACCES
117 Permission denied
118
119
120 EBUSY
121 The partition was opened exclusively by another thread
122
123
124 EFAULT
125 The argument features a bad address
126
127
128 EINVAL
129 Invalid argument
130
139
140
141 EROFS
142 The device is read-only
143
144
145 EAGAIN
146 Resource temporarily unavailable
147
148
149 EINTR
150 A signal was caught during the execution of the ioctl()
151 function
152
153
154 ENOMEM
155 Insufficient memory
156
157
158 EPERM
159 Insufficent access permission
160
161
162 EIO
163 An I/O error occurred. Refer to notes for details on copy-
164 protected DVD-ROM media.
165
166
167 CONFIGURATION
168 The sd driver can be configured by defining properties in the sd.conf
169 file. The sd driver supports the following properties:
170
171 enable-partition-kstats
172 The default value is 1, which causes
173 partition IO statistics to be maintained.
174 Set this value to zero to prevent the driver
175 from recording partition statistics. This
176 slightly reduces the CPU overhead for IO,
177 mimimizes the amount of sar(1) data
178 collected and makes these statistics
179 unavailable for reporting by iostat(1M) even
531
532 Unable to read label
533
534 Failure to read disk label.
535
536
537 Unit does not respond to selection
538
539 Drive went offline; probably powered down.
540
541
542 NOTES
543 DVD-ROM media containing DVD-Video data may follow/adhere to the
544 requirements of content scrambling system or copy protection scheme.
545 Reading of copy-protected sector will cause I/O error. Users are
546 advised to use the appropriate playback software to view video contents
547 on DVD-ROM media containing DVD-Video data.
548
549
550
551 May 13, 2017 SD(7D)
|
15 read or write to the device that happens after the open results in the
16 label being read if the label is not currently valid. Once read, the
17 label remains valid until the last close of the device. Except for
18 reading the label, O_NDELAY has no impact on the driver.
19
20 SPARC
21 The sd SCSI and SCSI/ATAPI driver supports embedded SCSI-2 and
22 CCS-compatible SCSI disk and CD-ROM drives, ATAPI 2.6
23 (SFF-8020i)-compliant CD-ROM drives, SFF-8090-compliant SCSI/ATAPI DVD-
24 ROM drives, IOMEGA SCSI/ATAPI ZIP drives, SCSI JAZ drives, and USB mass
25 storage devices (refer to scsa2usb(7D)).
26
27
28 To determine the disk drive type, use the SCSI/ATAPI inquiry command
29 and read the volume label stored on block 0 of the drive. (The volume
30 label describes the disk geometry and partitioning and must be present
31 for the disk to be mounted by the system.) A volume label is not
32 required for removable, re-writable or read-only media.
33
34 x86 Only
35 The sd driver supports embedded SCSI-2 and CCS-compatible SCSI disk and
36 CD-ROM drives, ATAPI 2.6 (SFF-8020i)-compliant CD-ROM drives,
37 SFF-8090-compliant SCSI/ATAPI DVD-ROM drives, IOMEGA SCSI/ATAPI ZIP
38 drives, and SCSI JAZ drives.
39
40
41 The x86 BIOS legacy requires a master boot record (MBR) and fdisk table
42 in the first physical sector of the bootable media. If the x86 hard
43 disk contains a Solaris disk label, it is located in the second
44 512-byte sector of the FDISK partition.
45
46 DEVICE SPECIAL FILES
47 Block-files access the disk using normal buffering mechanism and are
48 read-from and written-to without regard to physical disk records. A raw
49 interface enables direct transmission between the disk and the user's
50 read or write buffer. A single read or write call usually results in a
51 single I/O operation, therefore raw I/O is more efficient when many
52 bytes are transmitted. Block files names are found in /dev/dsk; raw
53 file names are found in /dev/rdsk.
54
55
90 the appropriate drive.
91
92
93 When a ZIP/JAZ drive is opened, the eject button is disabled to prevent
94 the manual removal of a disk until the last close() is called. No
95 volume label is required for a ZIP/JAZ drive. If the ZIP/JAZ drive
96 contains data recorded in a Solaris-aware file system format, it can be
97 mounted using the appropriate Solaris file system support.
98
99 DEVICE STATISTICS SUPPORT
100 Each device maintains I/O statistics for the device and for partitions
101 allocated for that device. For each device/partition, the driver
102 accumulates reads, writes, bytes read, and bytes written. The driver
103 also initiates hi-resolution time stamps at queue entry and exit points
104 to enable monitoring of residence time and cumulative residence-length
105 product for each queue.
106
107
108 Not all device drivers make per-partition IO statistics available for
109 reporting. sd and ssd(7D) per-partition statistics are enabled by
110 default but may be disabled in their configuration files.
111
112 IOCTLS
113 Refer to dkio(7I), and cdio(7I)
114
115 ERRORS
116 EACCES
117 Permission denied
118
119
120 EBUSY
121 The partition was opened exclusively by another thread
122
123
124 EFAULT
125 The argument features a bad address
126
127
128 EINVAL
129 Invalid argument
130
139
140
141 EROFS
142 The device is read-only
143
144
145 EAGAIN
146 Resource temporarily unavailable
147
148
149 EINTR
150 A signal was caught during the execution of the ioctl()
151 function
152
153
154 ENOMEM
155 Insufficient memory
156
157
158 EPERM
159 Insufficient access permission
160
161
162 EIO
163 An I/O error occurred. Refer to notes for details on copy-
164 protected DVD-ROM media.
165
166
167 CONFIGURATION
168 The sd driver can be configured by defining properties in the sd.conf
169 file. The sd driver supports the following properties:
170
171 enable-partition-kstats
172 The default value is 1, which causes
173 partition IO statistics to be maintained.
174 Set this value to zero to prevent the driver
175 from recording partition statistics. This
176 slightly reduces the CPU overhead for IO,
177 mimimizes the amount of sar(1) data
178 collected and makes these statistics
179 unavailable for reporting by iostat(1M) even
531
532 Unable to read label
533
534 Failure to read disk label.
535
536
537 Unit does not respond to selection
538
539 Drive went offline; probably powered down.
540
541
542 NOTES
543 DVD-ROM media containing DVD-Video data may follow/adhere to the
544 requirements of content scrambling system or copy protection scheme.
545 Reading of copy-protected sector will cause I/O error. Users are
546 advised to use the appropriate playback software to view video contents
547 on DVD-ROM media containing DVD-Video data.
548
549
550
551 January 10, 2020 SD(7D)
|