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