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