GC !__DragonFly__ section.
[dragonfly.git] / sbin / camcontrol / camcontrol.8
CommitLineData
984263bc
MD
1.\"
2.\" Copyright (c) 1998, 1999, 2000, 2002 Kenneth D. Merry.
3.\" All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\" notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\" notice, this list of conditions and the following disclaimer in the
12.\" documentation and/or other materials provided with the distribution.
13.\" 3. The name of the author may not be used to endorse or promote products
14.\" derived from this software without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\" $FreeBSD: src/sbin/camcontrol/camcontrol.8,v 1.19.2.12 2003/01/08 17:55:02 njl Exp $
9bb2a92d 29.\" $DragonFly: src/sbin/camcontrol/camcontrol.8,v 1.3 2004/03/11 12:28:53 hmp Exp $
984263bc
MD
30.\"
31.Dd September 14, 1998
32.Dt CAMCONTROL 8
33.Os
34.Sh NAME
35.Nm camcontrol
36.Nd CAM control program
37.Sh SYNOPSIS
38.Nm
39.Aq Ar command
40.Op device id
41.Op generic args
42.Op command args
43.Nm
44.Ic devlist
45.Op Fl v
46.Nm
47.Ic periphlist
48.Op device id
49.Op Fl n Ar dev_name
50.Op Fl u Ar unit_number
51.Nm
52.Ic tur
53.Op device id
54.Op generic args
55.Nm
56.Ic inquiry
57.Op device id
58.Op generic args
59.Op Fl D
60.Op Fl S
61.Op Fl R
62.Nm
63.Ic start
64.Op device id
65.Op generic args
66.Nm
67.Ic stop
68.Op device id
69.Op generic args
70.Nm
71.Ic eject
72.Op device id
73.Op generic args
74.Nm
75.Ic rescan
76.Aq all | bus Ns Op :target:lun
77.Nm
78.Ic reset
79.Aq all | bus Ns Op :target:lun
80.Nm
81.Ic defects
82.Op device id
83.Op generic args
84.Aq Fl f Ar format
85.Op Fl P
86.Op Fl G
87.Nm
88.Ic modepage
89.Op device id
90.Op generic args
91.Aq Fl m Ar page
92.Op Fl P Ar pgctl
93.Op Fl e
94.Op Fl d
95.Nm
96.Ic cmd
97.Op device id
98.Op generic args
99.Aq Fl c Ar cmd Op args
100.Op Fl i Ar len Ar fmt
101.Bk -words
102.Op Fl o Ar len Ar fmt Op args
103.Ek
104.Nm
105.Ic debug
106.Op Fl I
107.Op Fl P
108.Op Fl T
109.Op Fl S
110.Op Fl X
111.Op Fl c
112.Aq all|off|bus Ns Op :target Ns Op :lun
113.Nm
114.Ic tags
115.Op device id
116.Op generic args
117.Op Fl N Ar tags
118.Op Fl q
119.Op Fl v
120.Nm
121.Ic negotiate
122.Op device id
123.Op generic args
124.Op Fl c
125.Op Fl D Ar enable|disable
126.Op Fl O Ar offset
127.Op Fl q
128.Op Fl R Ar syncrate
129.Op Fl T Ar enable|disable
130.Op Fl U
131.Op Fl W Ar bus_width
132.Op Fl v
133.Nm
134.Ic format
135.Op device id
136.Op generic args
137.Op Fl q
138.Op Fl w
139.Op Fl y
140.Nm
141.Ic help
142.Sh DESCRIPTION
143The
144.Nm
145utility is designed to provide a way for users to access and control the
9bb2a92d 146.Dx
984263bc
MD
147CAM subsystem.
148.Pp
149The
150.Nm
151utility
152can cause a loss of data and/or system crashes if used improperly. Even
153expert users are encouraged to exercise caution when using this command.
154Novice users should stay away from this utility.
155.Pp
156The
157.Nm
158utility has a number of primary functions, many of which support an optional
159device identifier. A device identifier can take one of three forms:
160.Bl -tag -width 14n
161.It deviceUNIT
162Specify a device name and unit number combination, like "da5" or "cd3".
163Note that character device node names (e.g. /dev/da0) are
164.Em not
165allowed here.
166.It bus:target
167Specify a bus number and target id. The bus number can be determined from
168the output of
169.Dq camcontrol devlist .
170The lun defaults to 0.
171.It bus:target:lun
172Specify the bus, target and lun for a device. (e.g. 1:2:0)
173.El
174.Pp
175The device identifier, if it is specified,
176.Em must
177come immediately after the function name, and before any generic or
178function-specific arguments. Note that the
179.Fl n
180and
181.Fl u
182arguments described below will override any device name or unit number
183specified beforehand. The
184.Fl n
185and
186.Fl u
187arguments will
188.Em not
189override a specified bus:target or bus:target:lun, however.
190.Pp
191Most of the
192.Nm
193primary functions support these generic arguments:
194.Bl -tag -width 14n
195.It Fl C Ar count
196SCSI command retry count. In order for this to work, error recovery
197.Pq Fl E
198must be turned on.
199.It Fl E
200Instruct the kernel to perform generic SCSI error recovery for the given
201command. This is needed in order for the retry count
202.Pq Fl C
203to be honored. Other than retrying commands, the generic error recovery in
204the code will generally attempt to spin up drives that are not spinning.
205It may take some other actions, depending upon the sense code returned from
206the command.
207.It Fl n Ar dev_name
208Specify the device type to operate on, e.g. "da", "cd".
209.It Fl t Ar timeout
210SCSI command timeout in seconds. This overrides the default timeout for
211any given command.
212.It Fl u Ar unit_number
213Specify the device unit number, e.g. "1", "5".
214.It Fl v
215Be verbose, print out sense information for failed SCSI commands.
216.El
217.Pp
218Primary command functions:
219.Bl -tag -width periphlist
220.It Ic devlist
221List all physical devices (logical units) attached to the CAM subsystem.
222This also includes a list of peripheral drivers attached to each device.
223With the
224.Fl v
225argument, SCSI bus number, adapter name and unit numbers are printed as
226well.
227.It Ic periphlist
228List all peripheral drivers attached to a given physical device (logical
229unit).
230.It Ic tur
231Send the SCSI test unit ready (0x00) command to the given device.
232The
233.Nm
234utility will report whether the device is ready or not.
235.It Ic inquiry
236Send a SCSI inquiry command (0x12) to a device. By default,
237.Nm
238will print out the standard inquiry data, device serial number, and
239transfer rate information. The user can specify that only certain types of
240inquiry data be printed:
241.Bl -tag -width 4n
242.It Fl D
243Get the standard inquiry data.
244.It Fl S
245Print out the serial number. If this flag is the only one specified,
246.Nm
247will not print out "Serial Number" before the value returned by the drive.
248This is to aid in script writing.
249.It Fl R
250Print out transfer rate information.
251.El
252.It Ic start
253Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
254start bit set.
255.It Ic stop
256Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
257start bit cleared.
258.It Ic eject
259Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
260start bit cleared and the eject bit set.
261.It Ic rescan
262Tell the kernel to scan all busses in the system (with the
263.Ar all
264argument), the given bus (XPT_SCAN_BUS), or bus:target:lun
265(XPT_SCAN_LUN) for new devices or devices that have gone away. The user
266may specify a scan of all busses, a single bus, or a lun. Scanning all luns
267on a target isn't supported.
268.It Ic reset
269Tell the kernel to reset all busses in the system (with the
270.Ar all
271argument) or the given bus (XPT_RESET_BUS) by issuing a SCSI bus
272reset for that bus, or to reset the given bus:target:lun
273(XPT_RESET_DEV), typically by issuing a BUS DEVICE RESET message after
274connecting to that device.
275Note that this can have a destructive impact
276on the system.
277.It Ic defects
278Send the SCSI READ DEFECT DATA (10) command (0x37) to the given device, and
279print out any combination of: the total number of defects, the primary
280defect list (PLIST), and the grown defect list (GLIST).
281.Bl -tag -width 11n
282.It Fl f Ar format
283The three format options are:
284.Em block ,
285to print out the list as logical blocks,
286.Em bfi ,
287to print out the list in bytes from index format, and
288.Em phys ,
289to print out the list in physical sector format. The format argument is
290required. Most drives support the physical sector format. Some drives
291support the logical block format. Many drives, if they don't support the
292requested format, return the data in an alternate format, along with sense
293information indicating that the requested data format isn't supported.
294The
295.Nm
296utility
297attempts to detect this, and print out whatever format the drive returns.
298If the drive uses a non-standard sense code to report that it doesn't
299support the requested format,
300.Nm
301will probably see the error as a failure to complete the request.
302.It Fl G
303Print out the grown defect list. This is a list of bad blocks that have
304been remapped since the disk left the factory.
305.It Fl P
306Print out the primary defect list.
307.El
308.Pp
309If neither
310.Fl P
311nor
312.Fl G
313is specified,
314.Nm
315will print out the number of defects given in the READ DEFECT DATA header
316returned from the drive.
317.It Ic modepage
318Allows the user to display and optionally edit a SCSI mode page. The mode
319page formats are located in
320.Pa /usr/share/misc/scsi_modes .
321This can be overridden by specifying a different file in the
322.Ev SCSI_MODES
323environment variable.
324The
325.Ic modepage
326command takes several arguments:
327.Bl -tag -width 12n
328.It Fl d
329Disable block descriptors for mode sense.
330.It Fl e
331This flag allows the user to edit values in the mode page.
332.It Fl m Ar mode_page
333This specifies the number of the mode page the user would like to view
334and/or edit. This argument is mandatory.
335.It Fl P Ar pgctl
336This allows the user to specify the page control field. Possible values are:
337.Bl -tag -width xxx -compact
338.It 0
339Current values
340.It 1
341Changeable values
342.It 2
343Default values
344.It 3
345Saved values
346.El
347.El
348.It Ic cmd
349Allows the user to send an arbitrary SCSI CDB to any device.
350The
351.Ic cmd
352function requires the
353.Fl c
354argument to specify the CDB. Other arguments are optional, depending on
355the command type. The command and data specification syntax is documented
356in
357.Xr cam_cdbparse 3 .
358NOTE: If the CDB specified causes data to be transfered to or from the
359SCSI device in question, you MUST specify either
360.Fl i
361or
362.Fl o .
363.Bl -tag -width 17n
364.It Fl c Ar cmd Op args
365This specifies the SCSI CDB. CDBs may be 6, 10, 12 or 16 bytes.
366.It Fl i Ar len Ar fmt
367This specifies the amount of data to read, and how it should be displayed.
368If the format is
369.Sq - ,
370.Ar len
371bytes of data will be read from the device and written to standard output.
372.It Fl o Ar len Ar fmt Op args
373This specifies the amount of data to be written to a device, and the data
374that is to be written. If the format is
375.Sq - ,
376.Ar len
377bytes of data will be read from standard input and written to the device.
378.El
379.It Ic debug
380Turn on CAM debugging printfs in the kernel. This requires options CAMDEBUG
381in your kernel config file. WARNING: enabling debugging printfs currently
382causes an EXTREME number of kernel printfs. You may have difficulty
383turning off the debugging printfs once they start, since the kernel will be
384busy printing messages and unable to service other requests quickly.
385The
386.Ic debug
387function takes a number of arguments:
388.Bl -tag -width 18n
389.It Fl I
390Enable CAM_DEBUG_INFO printfs.
391.It Fl P
392Enable CAM_DEBUG_PERIPH printfs.
393.It Fl T
394Enable CAM_DEBUG_TRACE printfs.
395.It Fl S
396Enable CAM_DEBUG_SUBTRACE printfs.
397.It Fl X
398Enable CAM_DEBUG_XPT printfs.
399.It Fl c
400Enable CAM_DEBUG_CDB printfs. This will cause the kernel to print out the
401SCSI CDBs sent to the specified device(s).
402.It all
403Enable debugging for all devices.
404.It off
405Turn off debugging for all devices
406.It bus Ns Op :target Ns Op :lun
407Turn on debugging for the given bus, target or lun. If the lun or target
408and lun are not specified, they are wildcarded. (i.e., just specifying a
409bus turns on debugging printfs for all devices on that bus.)
410.El
411.It Ic tags
412Show or set the number of "tagged openings" or simultaneous transactions
413we attempt to queue to a particular device. By default, the
414.Ic tags
415command, with no command-specific arguments (i.e. only generic arguments)
416prints out the "soft" maximum number of transactions that can be queued to
417the device in question. For more detailed information, use the
418.Fl v
419argument described below.
420.Bl -tag -width 7n
421.It Fl N Ar tags
422Set the number of tags for the given device. This must be between the
423minimum and maximum number set in the kernel quirk table. The default for
424most devices that support tagged queueing is a minimum of 2 and a maximum
425of 255. The minimum and maximum values for a given device may be
426determined by using the
427.Fl v
428switch. The meaning of the
429.Fl v
430switch for this
431.Nm
432subcommand is described below.
433.It Fl q
434Be quiet, and don't report the number of tags. This is generally used when
435setting the number of tags.
436.It Fl v
437The verbose flag has special functionality for the
438.Em tags
439argument. It causes
440.Nm
441to print out the tagged queueing related fields of the XPT_GDEV_TYPE CCB:
442.Bl -tag -width 13n
443.It dev_openings
444This is the amount of capacity for transactions queued to a given device.
445.It dev_active
446This is the number of transactions currently queued to a device.
447.It devq_openings
448This is the kernel queue space for transactions. This count usually mirrors
449dev_openings except during error recovery operations when
450the device queue is frozen (device is not allowed to receive
451commands), the number of dev_openings is reduced, or transaction
452replay is occurring.
453.It devq_queued
454This is the number of transactions waiting in the kernel queue for capacity
455on the device. This number is usually zero unless error recovery is in
456progress.
457.It held
458The held count is the number of CCBs held by peripheral drivers that have
459either just been completed or are about to be released to the transport
460layer for service by a device. Held CCBs reserve capacity on a given
461device.
462.It mintags
463This is the current "hard" minimum number of transactions that can be
464queued to a device at once. The
465.Ar dev_openings
466value above cannot go below this number. The default value for
467.Ar mintags
468is 2, although it may be set higher or lower for various devices.
469.It maxtags
470This is the "hard" maximum number of transactions that can be queued to a
471device at one time. The
472.Ar dev_openings
473value cannot go above this number. The default value for
474.Ar maxtags
475is 255, although it may be set higher or lower for various devices.
476.El
477.El
478.It Ic negotiate
479Show or negotiate various communication parameters. Some controllers may
480not support setting or changing some of these values. For instance, the
481Adaptec 174x controllers do not support changing a device's sync rate or
482offset.
483The
484.Nm
485utility
486will not attempt to set the parameter if the controller indicates that it
487does not support setting the parameter. To find out what the controller
488supports, use the
489.Fl v
490flag. The meaning of the
491.Fl v
492flag for the
493.Ic negotiate
494command is described below. Also, some controller drivers don't support
495setting negotiation parameters, even if the underlying controller supports
496negotiation changes. Some controllers, such as the Advansys wide
497controllers, support enabling and disabling synchronous negotiation for
498a device, but do not support setting the synchronous negotiation rate.
499.Bl -tag -width 17n
500.It Fl a
501Attempt to make the negotiation settings take effect immediately by sending
502a Test Unit Ready command to the device.
503.It Fl c
504Show or set current negotiation settings. This is the default.
505.It Fl D Ar enable|disable
506Enable or disable disconnection.
507.It Fl O Ar offset
508Set the command delay offset.
509.It Fl q
510Be quiet, don't print anything. This is generally useful when you want to
511set a parameter, but don't want any status information.
512.It Fl R Ar syncrate
513Change the synchronization rate for a device. The sync rate is a floating
514point value specified in MHz. So, for instance,
515.Sq 20.000
516is a legal value, as is
517.Sq 20 .
518.It Fl T Ar enable|disable
519Enable or disable tagged queueing for a device.
520.It Fl U
521Show or set user negotiation settings. The default is to show or set
522current negotiation settings.
523.It Fl v
524The verbose switch has special meaning for the
525.Ic negotiate
526subcommand. It causes
527.Nm
528to print out the contents of a Path Inquiry (XPT_PATH_INQ) CCB sent to the
529controller driver.
530.It Fl W Ar bus_width
531Specify the bus width to negotiate with a device. The bus width is
532specified in bits. The only useful values to specify are 8, 16, and 32
533bits. The controller must support the bus width in question in order for
534the setting to take effect.
535.El
536.Pp
537In general, sync rate and offset settings will not take effect for a
538device until a command has been sent to the device. The
539.Fl a
540switch above will automatically send a Test Unit Ready to the device so
541negotiation parameters will take effect.
542.It Ic format
543Issue the
544.Tn SCSI
545FORMAT UNIT command to the named device.
546.Pp
547.Em WARNING! WARNING! WARNING!
548.Pp
549Low level formatting a disk will destroy ALL data on the disk. Use
550extreme caution when issuing this command. Many users low-level format
551disks that do not really need to be low-level formatted. There are
552relatively few scenarios that call for low-level formatting a disk.
553One reason for
554low-level formatting a disk is to initialize the disk after changing
555its physical sector size. Another reason for low-level formatting a disk
556is to revive the disk if you are getting "medium format corrupted" errors
557from the disk in response to read and write requests.
558.Pp
559Some disks take longer than others to format. Users should specify a
560timeout long enough to allow the format to complete. The default format
561timeout is 3 hours, which should be long enough for most disks. Some hard
562disks will complete a format operation in a very short period of time
563(on the order of 5 minutes or less). This is often because the drive
564doesn't really support the FORMAT UNIT command -- it just accepts the
565command, waits a few minutes and then returns it.
566.Pp
567The
568.Sq format
569subcommand takes several arguments that modify its default behavior. The
570.Fl q
571and
572.Fl y
573arguments can be useful for scripts.
574.Pp
575.Bl -tag -width 6n
576.It Fl q
577Be quiet, don't print any status messages. This option will not disable
578the questions, however. To disable questions, use the
579.Fl y
580argument, below.
581.It Fl w
582Issue a non-immediate format command. By default,
583.Nm
584issues the FORMAT UNIT command with the immediate bit set. This tells the
585device to immediately return the format command, before the format has
586actually completed. Then,
587.Nm
588gathers
589.Tn SCSI
590sense information from the device every second to determine how far along
591in the format process it is. If the
592.Fl w
593argument is specified,
594.Nm
595will issue a non-immediate format command, and will be unable to print any
596information to let the user know what percentage of the disk has been
597formatted.
598.It Fl y
599Don't ask any questions. By default,
600.Nm
601will ask the user if he/she really wants to format the disk in question,
602and also if the default format command timeout is acceptable. The user
603will not be asked about the timeout if a timeout is specified on the
604command line.
605.El
606.It Ic help
607Print out verbose usage information.
608.El
609.Sh ENVIRONMENT
610The
611.Ev SCSI_MODES
612variable allows the user to specify an alternate mode page format file.
613.Pp
614The
615.Ev EDITOR
616variable determines which text editor
617.Nm
618starts when editing mode pages.
619.Sh FILES
620.Bl -tag -width /usr/share/misc/scsi_modes -compact
621.It Pa /usr/share/misc/scsi_modes
622is the SCSI mode format database.
623.It Pa /dev/xpt0
624is the transport layer device.
625.It Pa /dev/pass*
626are the CAM application passthrough devices.
627.El
628.Sh EXAMPLES
629.Dl camcontrol eject -n cd -u 1 -v
630.Pp
631Eject the CD from cd1, and print SCSI sense information if the command
632fails.
633.Pp
634.Dl camcontrol tur da0
635.Pp
636Send the SCSI test unit ready command to da0.
637The
638.Nm
639utility will report whether the disk is ready, but will not display sense
640information if the command fails since the
641.Fl v
642switch was not specified.
643.Pp
644.Bd -literal -offset indent
645camcontrol tur da1 -E -C 4 -t 50 -v
646.Ed
647.Pp
648Send a test unit ready command to da1. Enable kernel error recovery.
649Specify a retry count of 4, and a timeout of 50 seconds. Enable sense
650printing (with the
651.Fl v
652flag) if the command fails. Since error recovery is turned on, the
653disk will be spun up if it is not currently spinning.
654The
655.Nm
656utility will report whether the disk is ready.
657.Bd -literal -offset indent
658camcontrol cmd -n cd -u 1 -v -c "3C 00 00 00 00 00 00 00 0e 00" \e
659 -i 0xe "s1 i3 i1 i1 i1 i1 i1 i1 i1 i1 i1 i1"
660.Ed
661.Pp
662Issue a READ BUFFER command (0x3C) to cd1. Display the buffer size of cd1,
663and display the first 10 bytes from the cache on cd1. Display SCSI sense
664information if the command fails.
665.Pp
666.Bd -literal -offset indent
667camcontrol cmd -n cd -u 1 -v -c "3B 00 00 00 00 00 00 00 0e 00" \e
668 -o 14 "00 00 00 00 1 2 3 4 5 6 v v v v" 7 8 9 8
669.Ed
670.Pp
671Issue a WRITE BUFFER (0x3B) command to cd1. Write out 10 bytes of data,
672not including the (reserved) 4 byte header. Print out sense information if
673the command fails. Be very careful with this command, improper use may
674cause data corruption.
675.Pp
676.Bd -literal -offset indent
677camcontrol modepage da3 -m 1 -e -P 3
678.Ed
679.Pp
680Edit mode page 1 (the Read-Write Error Recover page) for da3, and save the
681settings on the drive. Mode page 1 contains a disk drive's auto read and
682write reallocation settings, among other things.
683.Pp
684.Dl camcontrol rescan all
685.Pp
686Rescan all SCSI busses in the system for devices that have been added,
687removed or changed.
688.Pp
689.Dl camcontrol rescan 0
690.Pp
691Rescan SCSI bus 0 for devices that have been added, removed or changed.
692.Pp
693.Dl camcontrol rescan 0:1:0
694.Pp
695Rescan SCSI bus 0, target 1, lun 0 to see if it has been added, removed, or
696changed.
697.Pp
698.Dl camcontrol tags da5 -N 24
699.Pp
700Set the number of concurrent transactions for da5 to 24.
701.Pp
702.Bd -literal -offset indent
703camcontrol negotiate -n da -u 4 -T disable
704.Ed
705.Pp
706Disable tagged queueing for da4.
707.Pp
708.Bd -literal -offset indent
709camcontrol negotiate -n da -u 3 -R 20.000 -O 15 -a
710.Ed
711.Pp
712Negotiate a sync rate of 20MHz and an offset of 15 with da3. Then send a
713Test Unit Ready command to make the settings take effect.
714.Sh SEE ALSO
715.Xr cam 3 ,
716.Xr cam_cdbparse 3 ,
717.Xr cam 4 ,
718.Xr pass 4 ,
719.Xr xpt 4
720.Sh HISTORY
721The
722.Nm
723utility first appeared in
724.Fx 3.0 .
725.Pp
726The mode page editing code and arbitrary SCSI command code are based upon
727code in the old
728.Xr scsi 8
729utility and
730.Xr scsi 3
731library, written by Julian Elischer and Peter Dufault. The
732.Xr scsi 8
733program first appeared in
734.Bx 386 0.1.2.4 ,
735and first appeared in
736.Fx
737in
738.Fx 2.0.5 .
739.Sh AUTHORS
740.An Kenneth Merry Aq ken@FreeBSD.org
741.Sh BUGS
742The code that parses the generic command line arguments doesn't know that
743some of the subcommands take multiple arguments. So if, for instance, you
744tried something like this:
745.Bd -literal -offset indent
746camcontrol cmd -n da -u 1 -c "00 00 00 00 00 v" 0x00 -v
747.Ed
748.Pp
749The sense information from the test unit ready command would not get
750printed out, since the first
751.Xr getopt 3
752call in
753.Nm
754bails out when it sees the second argument to
755.Fl c
756(0x00),
757above. Fixing this behavior would take some gross code, or changes to the
758.Xr getopt 3
759interface. The best way to circumvent this problem is to always make sure
760to specify generic
761.Nm
762arguments before any command-specific arguments.