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