1 .\" @(#)scgcheck.1 1.4 01/04/16 Copyright 2000 J. Schilling
3 .\" This is free documentation; you can redistribute it and/or
4 .\" modify it under the terms of the GNU General Public License as
5 .\" published by the Free Software Foundation; either version 2 of
6 .\" the License, or (at your option) any later version.
8 .\" The GNU General Public License's references to "object code"
9 .\" and "executables" are to be interpreted as the output of any
10 .\" document formatting or typesetting system, including
11 .\" intermediate and printed output.
13 .\" This manual is distributed in the hope that it will be useful,
14 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
15 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 .\" GNU General Public License for more details.
18 .\" You should have received a copy of the GNU General Public
19 .\" License along with this manual; if not, write to the Free
20 .\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
23 .if t .ds a \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'a
24 .if t .ds o \v'-0.55m'\h'0.00n'\z.\h'0.45n'\z.\v'0.55m'\h'-0.45n'o
25 .if t .ds u \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'u
26 .if t .ds A \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'A
27 .if t .ds O \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'O
28 .if t .ds U \v'-0.77m'\h'0.30n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.75n'U
35 .TH SCGCHECK 1 "Version 1.10" "J\*org Schilling" "Schily\'s USER COMMANDS"
37 scgcheck \- check and validate the ABI of libscg
46 is used to check and verify the Application Binary Interface of libscg.
52 .IR scsibus / target / lun
53 of the drive. Communication on
55 is done with the SCSI general driver
57 Other operating systems are using a library simulation of this driver.
60 .IR scsibus , target , lun
64 In the latter case, the drive has to be connected to the default
65 SCSI bus of the machine.
71 Some operating systems or SCSI transport implementations may require to
72 specify a filename in addition.
73 In this case the correct syntax for the device is:
75 .IR devicename : scsibus , target , lun
78 .IR devicename : target , lun .
79 If the name of the device node that has been specified on such a system
80 refers to exactly one SCSI device, a shorthand in the form
85 .IR devicename : @ , lun
86 may be used instead of
88 .IR devicename : scsibus , target , lun .
91 To access remote SCSI devices, you need to prepend the SCSI device name by
92 a remote device indicator. The remote device indicator is either
93 .BI REMOTE: user@host:
98 A valid remote SCSI device name may be:
99 .BI REMOTE: user@host:
100 to allow remote SCSI bus scanning or
101 .BI REMOTE: user@host:1,0,0
102 to access the SCSI device at
104 connected to SCSI bus # 1,target 0 lun 0.
109 portable to all \s-2UNIX\s0 platforms, the syntax
111 .IR devicename : scsibus , target , lun
112 is preferred as is hides OS specific knowledge about device names from the user.
113 A specific OS must not necessarily support a way to specify a real device file name nor a
115 .IR scsibus , target , lun .
119 0 is the default SCSI bus on the machine. Watch the boot messages for more
120 information or look into
122 for more information about the SCSI configuration of your machine.
123 If you have problems to figure out what values for
124 .IR scsibus , target , lun
125 should be used, try the
133 Print version information and exit.
136 Sets the SCSI target default for SCSI Bus scanning test, see notes above.
137 This allows e.g. to specify to use Solaris USCSI or remote SCSI
138 for the bus scanning case.
140 For the non bus scanning case, a typical device specification is
143 If a filename must be provided together with the numerical target
144 specification, the filename is implementation specific.
145 The correct filename in this case can be found in the system specific
146 manuals of the target operating system.
151 support, you need to use the control device (e.g.
153 A correct device specification in this case may be
154 .BI dev= /dev/rcd0.ctl:@
157 On Linux, drives connected to a parallel port adapter are mapped
158 to a virtual SCSI bus. Different adapters are mapped to different
159 targets on this virtual SCSI bus.
165 will try to get the device from the
169 If the argument to the
171 option does not contain the characters ',', '/', '@' or ':',
172 it is interpreted as an label name that may be found in the file
173 /etc/default/cdrecord (see FILES section).
176 Set the default SCSI command timeout value to
178 The default SCSI command timeout is the minimum timeout used for sending
180 If a SCSI command fails due to a timeout, you may try to raise the
181 default SCSI command timeout above the timeout value of the failed command.
182 If the command runs correctly with a raised command timeout,
183 please report the better timeout value and the corresponding command to
184 the author of the program.
187 option is present, a default timeout of 40 seconds is used.
190 Set the misc debug value to # (with debug=#) or increment
191 the misc debug level by one (with -d). If you specify
195 This may help to find problems while opening a driver for libscg.
196 as well as with sector sizes and sector types.
199 slows down the process and may be the reason for a buffer underrun.
201 .BR kdebug= "#, " kd= #
204 to modify the kernel debug value while SCSI commands are running.
206 .BR \-silent ", " \-s
207 Do not print out a status report for failed SCSI commands.
210 Increment the level of general verbosity by one.
211 This is used e.g. to display the progress of the process.
214 Increment the verbose level with respect of SCSI command transport by one.
215 This helps to debug problems
216 during the process, that occur in the CD-Recorder.
217 If you get incomprehensible error messages you should use this flag
218 to get more detailed output.
220 will show data buffer content in addition.
225 slows down the process.
228 Specify the log file to be used instead of
245 .B "Linux SCSI generic driver."
248 uses a hack, that tries to emulate the functionality of the scg driver.
249 Unfortunately, the sg driver on
251 has several severe bugs:
254 It cannot see if a SCSI command could not be sent at all.
257 It cannot get the SCSI status byte.
259 for that reason cannot report failing SCSI commands in some
263 It cannot get real DMA count of transfer.
265 cannot tell you if there is an DMA residual count.
268 It cannot get number of bytes valid in auto sense data.
270 cannot tell you if device transfers no sense data at all.
273 It fetches to few data in auto request sense (CCS/SCSI-2/SCSI-3 needs >= 18).
278 A typical error message for a SCSI command looks like:
282 readcd: I/O error. test unit ready: scsi sendcmd: no error
283 CDB: 00 20 00 00 00 00
284 status: 0x2 (CHECK CONDITION)
285 Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
286 Sense Key: 0x5 Illegal Request, Segment 0
287 Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
288 Sense flags: Blk 0 (not valid)
289 cmd finished after 0.002s timeout 40s
293 The first line gives information about the transport of the command.
294 The text after the first colon gives the error text for the system call
295 from the view of the kernel. It usually is:
297 unless other problems happen. The next words contain a short description for
298 the SCSI command that fails. The rest of the line tells you if there were
299 any problems for the transport of the command over the SCSI bus.
301 means that it was not possible to transport the command (i.e. no device present
302 at the requested SCSI address).
304 The second line prints the SCSI command descriptor block for the failed command.
306 The third line gives information on the SCSI status code returned by the
307 command, if the transport of the command succeeds.
308 This is error information from the SCSI device.
310 The fourth line is a hex dump of the auto request sense information for the
313 The fifth line is the error text for the sense key if available, followed
314 by the segment number that is only valid if the command was a
316 command. If the error message is not directly related to the current command,
321 The sixth line is the error text for the sense code and the sense qualifier if available.
322 If the type of the device is known, the sense data is decoded from tables
325 The text is followed by the error value for a field replaceable unit.
327 The seventh line prints the block number that is related to the failed command
328 and text for several error flags. The block number may not be valid.
330 The eight line reports the timeout set up for this commans and the time
331 that the command realy needed to be finished.
347 Additional information can be found on:
349 http://www.fokus.gmd.de/usr/schilling/cdrecord.html
351 If you have support questions, send them to:
354 cdrecord-support@berlios.de
358 other-cdwrite@lists.debian.org
360 Of you definitly found a bug, send a mail to:
363 cdrecord-developers@berlios.de
367 schilling@fokus.gmd.de
372 http://lists.berlios.de/mailman/listinfo/cdrecord-developers
376 http://lists.berlios.de/mailman/listinfo/cdrecord-support
OSDN Git Service
