2 .\" Copyright (c) 1998, 1999, 2000, 2002, 2005, 2006, 2007 Kenneth D. Merry.
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
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.
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
35 .Nd CAM control program
49 .Op Fl u Ar unit_number
72 .Op Fl r Ar reporttype
101 .Aq all | bus Ns Op :target:lun
104 .Aq all | bus Ns Op :target:lun
116 .Aq Fl m Ar page | Fl l
124 .Aq Fl a Ar cmd Op args
125 .Aq Fl c Ar cmd Op args
128 .Op Fl i Ar len Ar fmt
130 .Op Fl o Ar len Ar fmt Op args
137 .Aq Fl r Ar len Ar fmt Op args
138 .Aq Fl R Ar len Ar fmt Op args
150 .Op Fl o Ar operation
154 .Op Fl T Ar pp_timeout
155 .Op Fl a Ar enable|disable
156 .Op Fl A Ar enable|disable
157 .Op Fl s Ar enable|disable
158 .Op Fl S Ar enable|disable
178 .Aq all|off|bus Ns Op :target Ns Op :lun
191 .Op Fl D Ar enable|disable
196 .Op Fl T Ar enable|disable
198 .Op Fl W Ar bus_width
227 utility is designed to provide a way for users to access and control the
234 can cause a loss of data and/or system crashes if used improperly.
236 expert users are encouraged to exercise caution when using this command.
237 Novice users should stay away from this utility.
241 utility has a number of primary functions, many of which support an optional
243 A device identifier can take one of three forms:
246 Specify a device name and unit number combination, like "da5" or "cd3".
248 Specify a bus number and target id.
249 The bus number can be determined from
251 .Dq camcontrol devlist .
252 The lun defaults to 0.
254 Specify the bus, target and lun for a device.
258 The device identifier, if it is specified,
260 come immediately after the function name, and before any generic or
261 function-specific arguments.
266 arguments described below will override any device name or unit number
267 specified beforehand.
274 override a specified bus:target or bus:target:lun, however.
278 primary functions support these generic arguments:
281 SCSI command retry count.
282 In order for this to work, error recovery
286 Instruct the kernel to perform generic SCSI error recovery for the given
288 This is needed in order for the retry count
291 Other than retrying commands, the generic error recovery in
292 the code will generally attempt to spin up drives that are not spinning.
293 It may take some other actions, depending upon the sense code returned from
296 Specify the device type to operate on, e.g.\& "da", "cd".
298 SCSI command timeout in seconds.
299 This overrides the default timeout for
301 .It Fl u Ar unit_number
302 Specify the device unit number, e.g.\& "1", "5".
304 Be verbose, print out sense information for failed SCSI commands.
307 Primary command functions:
308 .Bl -tag -width periphlist
310 List all physical devices (logical units) attached to the CAM subsystem.
311 This also includes a list of peripheral drivers attached to each device.
314 argument, SCSI bus number, adapter name and unit numbers are printed as
317 List all peripheral drivers attached to a given physical device (logical
320 Send the SCSI test unit ready (0x00) command to the given device.
323 utility will report whether the device is ready or not.
325 Send a SCSI inquiry command (0x12) to a device.
328 will print out the standard inquiry data, device serial number, and
329 transfer rate information.
330 The user can specify that only certain types of
331 inquiry data be printed:
334 Get the standard inquiry data.
336 Print out the serial number.
337 If this flag is the only one specified,
339 will not print out "Serial Number" before the value returned by the drive.
340 This is to aid in script writing.
342 Print out transfer rate information.
345 Send a ATA identify command (0xec) to a device.
347 Send the SCSI REPORT LUNS (0xA0) command to the given device.
350 will print out the list of logical units (LUNs) supported by the target device.
351 There are a couple of options to modify the output:
354 Just print out a count of LUNs, not the actual LUN numbers.
356 Just print out the LUNs, and don't print out the count.
357 .It Fl r Ar reporttype
358 Specify the type of report to request from the target:
359 .Bl -tag -width 012345678
361 Return the default report.
365 Most targets will support this report if they support the REPORT LUNS
368 Return only well known LUNs.
370 Return all available LUNs.
375 will try to print out LUN numbers in a reasonable format.
376 It can understand the peripheral, flat, LUN and extended LUN formats.
378 Send the SCSI READ CAPACITY command to the given device and display
380 If the device is larger than 2TB, the SCSI READ CAPACITY (16) service
381 action will be sent to obtain the full size of the device.
384 will print out the last logical block of the device, and the blocksize of
386 To modify the output format, use the following options:
389 Just print out the blocksize, not the last block or device size.
390 This cannot be used with
395 Print out the device size in human readable (base 2, 1K == 1024) format.
398 and cannot be used with
403 Print out the device size in human readable (base 10, 1K == 1000) format.
405 Print out the number of blocks in the device instead of the last logical
408 Quiet, print out the numbers only (separated by a comma if
414 Print out the last logical block or the size of the device only, and omit
418 Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
421 Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
424 Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
425 start bit set and the load/eject bit set.
427 Send the SCSI Start/Stop Unit (0x1B) command to the given device with the
428 start bit cleared and the load/eject bit set.
430 Tell the kernel to scan all busses in the system (with the
432 argument), the given bus (XPT_SCAN_BUS), or bus:target:lun
433 (XPT_SCAN_LUN) for new devices or devices that have gone away.
435 may specify a scan of all busses, a single bus, or a lun.
437 on a target is not supported.
439 Tell the kernel to reset all busses in the system (with the
441 argument) or the given bus (XPT_RESET_BUS) by issuing a SCSI bus
442 reset for that bus, or to reset the given bus:target:lun
443 (XPT_RESET_DEV), typically by issuing a BUS DEVICE RESET message after
444 connecting to that device.
445 Note that this can have a destructive impact
448 Send the SCSI READ DEFECT DATA (10) command (0x37) to the given device, and
449 print out any combination of: the total number of defects, the primary
450 defect list (PLIST), and the grown defect list (GLIST).
453 The three format options are:
455 to print out the list as logical blocks,
457 to print out the list in bytes from index format, and
459 to print out the list in physical sector format.
460 The format argument is
462 Most drives support the physical sector format.
464 support the logical block format.
465 Many drives, if they do not support the
466 requested format, return the data in an alternate format, along with sense
467 information indicating that the requested data format is not supported.
471 attempts to detect this, and print out whatever format the drive returns.
472 If the drive uses a non-standard sense code to report that it does not
473 support the requested format,
475 will probably see the error as a failure to complete the request.
477 Print out the grown defect list.
478 This is a list of bad blocks that have
479 been remapped since the disk left the factory.
481 Print out the primary defect list.
490 will print out the number of defects given in the READ DEFECT DATA header
491 returned from the drive.
493 Allows the user to display and optionally edit a SCSI mode page.
495 page formats are located in
496 .Pa /usr/share/misc/scsi_modes .
497 This can be overridden by specifying a different file in the
499 environment variable.
502 command takes several arguments:
505 Disable block descriptors for mode sense.
507 Displays mode page data in binary format.
509 This flag allows the user to edit values in the mode page.
511 either edit mode page values with the text editor pointed to by his
513 environment variable, or supply mode page values via standard input, using
516 uses to display mode page values.
517 The editor will be invoked if
519 detects that standard input is terminal.
521 Lists all available mode pages.
522 .It Fl m Ar mode_page
523 This specifies the number of the mode page the user would like to view
525 This argument is mandatory unless
529 This allows the user to specify the page control field.
531 .Bl -tag -width xxx -compact
543 Allows the user to send an arbitrary ATA or SCSI CDB to any device.
546 function requires the
548 argument to specify SCSI CDB or the
550 argument to specify ATA Command Block registers values.
551 Other arguments are optional, depending on
553 The command and data specification syntax is documented
556 NOTE: If the CDB specified causes data to be transferred to or from the
557 SCSI device in question, you MUST specify either
562 .It Fl a Ar cmd Op args
563 This specifies the content of 12 ATA Command Block registers (command,
564 features, lba_low, lba_mid, lba_high, device, lba_low_exp, lba_mid_exp.
565 lba_high_exp, features_exp, sector_count, sector_count_exp).
566 .It Fl c Ar cmd Op args
567 This specifies the SCSI CDB.
568 SCSI CDBs may be 6, 10, 12 or 16 bytes.
570 Specifies DMA protocol to be used for ATA command.
572 Specifies FPDMA (NCQ) protocol to be used for ATA command.
573 .It Fl i Ar len Ar fmt
574 This specifies the amount of data to read, and how it should be displayed.
578 bytes of data will be read from the device and written to standard output.
579 .It Fl o Ar len Ar fmt Op args
580 This specifies the amount of data to be written to a device, and the data
581 that is to be written.
585 bytes of data will be read from standard input and written to the device.
587 This specifies that 11 result ATA Command Block registers should be displayed
588 (status, error, lba_low, lba_mid, lba_high, device, lba_low_exp, lba_mid_exp,
589 lba_high_exp, sector_count, sector_count_exp), and how.
592 11 result registers will be written to standard output in hex.
595 Allows the user to send an arbitrary Serial
596 Management Protocol (SMP) command to a device.
599 function requires the
601 argument to specify the SMP request to be sent, and the
603 argument to specify the format of the SMP response.
604 The syntax for the SMP request and response arguments is documented in
607 Note that SAS adapters that support SMP passthrough (at least the currently
608 known adapters) do not accept CRC bytes from the user in the request and do
609 not pass CRC bytes back to the user in the response.
610 Therefore users should not include the CRC bytes in the length of the
611 request and not expect CRC bytes to be returned in the response.
613 .It Fl r Ar len Ar fmt Op args
614 This specifies the size of the SMP request, without the CRC bytes, and the
615 SMP request format. If the format is
618 bytes of data will be read from standard input and written as the SMP
620 .It Fl R Ar len Ar fmt Op args
621 This specifies the size of the buffer allocated for the SMP response, and
622 the SMP response format.
626 bytes of data will be allocated for the response and the response will be
627 written to standard output.
630 Allows the user to send the Serial Management Protocol (SMP) Report General
633 will display the data returned by the Report General command.
634 If the SMP target supports the long response format, the additional data
635 will be requested and displayed automatically.
638 Request the long response format only.
639 Not all SMP targets support the long response format.
642 to skip sending the initial report general request without the long bit set
643 and only issue a report general request with the long bit set.
646 Allows the user to issue the Serial Management Protocol (SMP) PHY Control
648 This function should be used with some caution, as it can render devices
649 inaccessible, and could potentially cause data corruption as well.
652 argument is required to specify the PHY to operate on.
655 Specify the PHY to operate on.
656 This argument is required.
658 Request the long request/response format.
659 Not all SMP targets support the long response format.
660 For the PHY Control command, this currently only affects whether the
661 request length is set to a value other than 0.
662 .It Fl o Ar operation
663 Specify a PHY control operation.
666 operation may be specified.
667 The operation may be specified numerically (in decimal, hexadecimal, or octal)
668 or one of the following operation names may be specified:
672 It is not necessary to specify this argument.
674 Send the LINK RESET command to the phy.
676 Send the HARD RESET command to the phy.
678 Send the DISABLE command to the phy.
679 Note that the LINK RESET or HARD RESET commands should re-enable the phy.
681 Send the CLEAR ERROR LOG command.
682 This clears the error log counters for the specified phy.
684 Send the CLEAR AFFILIATION command.
685 This clears the affiliation from the STP initiator port with the same SAS
686 address as the SMP initiator that requests the clear operation.
688 Send the TRANSMIT SATA PORT SELECTION SIGNAL command to the phy.
689 This will cause a SATA port selector to use the given phy as its active phy
690 and make the other phy inactive.
692 Send the CLEAR STP I_T NEXUS LOSS command to the PHY.
694 Send the SET ATTACHED DEVICE NAME command to the PHY.
697 argument to specify the device name.
700 Specify the attached device name.
701 This option is needed with the
704 The name is a 64-bit number, and can be specified in decimal, hexadecimal
707 Set the minimum physical link rate for the phy.
708 This is a numeric argument.
709 Currently known link rates are:
712 Do not change current value.
721 Other values may be specified for newer physical link rates.
723 Set the maximum physical link rate for the phy.
724 This is a numeric argument.
727 argument description for known link rate arguments.
728 .It Fl T Ar pp_timeout
729 Set the partial pathway timeout value, in microseconds.
734 specification for more information on this field.
735 .It Fl a Ar enable|disable
736 Enable or disable SATA slumber phy power conditions.
737 .It Fl A Ar enable|disable
738 Enable or disable SATA partial power conditions.
739 .It Fl s Ar enable|disable
740 Enable or disable SAS slumber phy power conditions.
741 .It Fl S Ar enable|disable
742 Enable or disable SAS partial phy power conditions.
745 List phys attached to a SAS expander, the address of the end device
746 attached to the phy, and the inquiry data for that device and peripheral
747 devices attached to that device.
748 The inquiry data and peripheral devices are displayed if available.
751 Turn on the long response format for the underlying SMP commands used for
754 Only print out phys that are attached to a device in the CAM EDT (Existing
758 Send the SMP Report Manufacturer Information command to the device and
759 display the response.
762 Turn on the long response format for the underlying SMP commands used for
766 Turn on CAM debugging printfs in the kernel.
767 This requires options CAMDEBUG
768 in your kernel config file.
769 WARNING: enabling debugging printfs currently
770 causes an EXTREME number of kernel printfs.
771 You may have difficulty
772 turning off the debugging printfs once they start, since the kernel will be
773 busy printing messages and unable to service other requests quickly.
776 function takes a number of arguments:
779 Enable CAM_DEBUG_INFO printfs.
781 Enable CAM_DEBUG_PERIPH printfs.
783 Enable CAM_DEBUG_TRACE printfs.
785 Enable CAM_DEBUG_SUBTRACE printfs.
787 Enable CAM_DEBUG_XPT printfs.
789 Enable CAM_DEBUG_CDB printfs.
790 This will cause the kernel to print out the
791 SCSI CDBs sent to the specified device(s).
793 Enable debugging for all devices.
795 Turn off debugging for all devices
796 .It bus Ns Op :target Ns Op :lun
797 Turn on debugging for the given bus, target or lun.
799 and lun are not specified, they are wildcarded.
800 (i.e., just specifying a
801 bus turns on debugging printfs for all devices on that bus.)
804 Show or set the number of "tagged openings" or simultaneous transactions
805 we attempt to queue to a particular device.
808 command, with no command-specific arguments (i.e., only generic arguments)
809 prints out the "soft" maximum number of transactions that can be queued to
810 the device in question.
811 For more detailed information, use the
813 argument described below.
816 Set the number of tags for the given device.
817 This must be between the
818 minimum and maximum number set in the kernel quirk table.
820 most devices that support tagged queueing is a minimum of 2 and a maximum
822 The minimum and maximum values for a given device may be
823 determined by using the
830 subcommand is described below.
832 Be quiet, and do not report the number of tags.
833 This is generally used when
834 setting the number of tags.
836 The verbose flag has special functionality for the
841 to print out the tagged queueing related fields of the XPT_GDEV_TYPE CCB:
844 This is the amount of capacity for transactions queued to a given device.
846 This is the number of transactions currently queued to a device.
848 This is the kernel queue space for transactions.
849 This count usually mirrors
850 dev_openings except during error recovery operations when
851 the device queue is frozen (device is not allowed to receive
852 commands), the number of dev_openings is reduced, or transaction
855 This is the number of transactions waiting in the kernel queue for capacity
857 This number is usually zero unless error recovery is in
860 The held count is the number of CCBs held by peripheral drivers that have
861 either just been completed or are about to be released to the transport
862 layer for service by a device.
863 Held CCBs reserve capacity on a given
866 This is the current "hard" minimum number of transactions that can be
867 queued to a device at once.
870 value above cannot go below this number.
871 The default value for
873 is 2, although it may be set higher or lower for various devices.
875 This is the "hard" maximum number of transactions that can be queued to a
879 value cannot go above this number.
880 The default value for
882 is 255, although it may be set higher or lower for various devices.
886 Show or negotiate various communication parameters.
888 not support setting or changing some of these values.
890 Adaptec 174x controllers do not support changing a device's sync rate or
895 will not attempt to set the parameter if the controller indicates that it
896 does not support setting the parameter.
897 To find out what the controller
905 command is described below.
906 Also, some controller drivers do not support
907 setting negotiation parameters, even if the underlying controller supports
909 Some controllers, such as the Advansys wide
910 controllers, support enabling and disabling synchronous negotiation for
911 a device, but do not support setting the synchronous negotiation rate.
914 Attempt to make the negotiation settings take effect immediately by sending
915 a Test Unit Ready command to the device.
917 Show or set current negotiation settings.
919 .It Fl D Ar enable|disable
920 Enable or disable disconnection.
924 Set the command delay offset.
926 Be quiet, do not print anything.
927 This is generally useful when you want to
928 set a parameter, but do not want any status information.
930 Change the synchronization rate for a device.
931 The sync rate is a floating
932 point value specified in MHz.
935 is a legal value, as is
937 .It Fl T Ar enable|disable
938 Enable or disable tagged queueing for a device.
940 Show or set user negotiation settings.
941 The default is to show or set
942 current negotiation settings.
944 The verbose switch has special meaning for the
949 to print out the contents of a Path Inquiry (XPT_PATH_INQ) CCB sent to the
951 .It Fl W Ar bus_width
952 Specify the bus width to negotiate with a device.
955 The only useful values to specify are 8, 16, and 32
957 The controller must support the bus width in question in order for
958 the setting to take effect.
961 In general, sync rate and offset settings will not take effect for a
962 device until a command has been sent to the device.
965 switch above will automatically send a Test Unit Ready to the device so
966 negotiation parameters will take effect.
970 FORMAT UNIT command to the named device.
972 .Em WARNING! WARNING! WARNING!
974 Low level formatting a disk will destroy ALL data on the disk.
976 extreme caution when issuing this command.
977 Many users low-level format
978 disks that do not really need to be low-level formatted.
980 relatively few scenarios that call for low-level formatting a disk.
982 low-level formatting a disk is to initialize the disk after changing
983 its physical sector size.
984 Another reason for low-level formatting a disk
985 is to revive the disk if you are getting "medium format corrupted" errors
986 from the disk in response to read and write requests.
988 Some disks take longer than others to format.
989 Users should specify a
990 timeout long enough to allow the format to complete.
992 timeout is 3 hours, which should be long enough for most disks.
994 disks will complete a format operation in a very short period of time
995 (on the order of 5 minutes or less).
996 This is often because the drive
997 does not really support the FORMAT UNIT command -- it just accepts the
998 command, waits a few minutes and then returns it.
1002 subcommand takes several arguments that modify its default behavior.
1007 arguments can be useful for scripts.
1010 Be quiet, do not print any status messages.
1011 This option will not disable
1012 the questions, however.
1013 To disable questions, use the
1020 This will report status on a format that is already running on the drive.
1022 Issue a non-immediate format command.
1025 issues the FORMAT UNIT command with the immediate bit set.
1027 device to immediately return the format command, before the format has
1033 sense information from the device every second to determine how far along
1034 in the format process it is.
1037 argument is specified,
1039 will issue a non-immediate format command, and will be unable to print any
1040 information to let the user know what percentage of the disk has been
1043 Do not ask any questions.
1046 will ask the user if he/she really wants to format the disk in question,
1047 and also if the default format command timeout is acceptable.
1049 will not be asked about the timeout if a timeout is specified on the
1053 Put ATA device into IDLE state. Optional parameter
1055 specifies automatic standby timer value in seconds. Value 0 disables timer.
1057 Put ATA device into STANDBY state. Optional parameter
1059 specifies automatic standby timer value in seconds. Value 0 disables timer.
1061 Put ATA device into SLEEP state. Note that the only way get device out of
1062 this state may be reset.
1064 Print out verbose usage information.
1069 variable allows the user to specify an alternate mode page format file.
1073 variable determines which text editor
1075 starts when editing mode pages.
1077 .Bl -tag -width /usr/share/misc/scsi_modes -compact
1078 .It Pa /usr/share/misc/scsi_modes
1079 is the SCSI mode format database.
1081 is the transport layer device.
1083 are the CAM application passthrough devices.
1086 .Dl camcontrol eject -n cd -u 1 -v
1088 Eject the CD from cd1, and print SCSI sense information if the command
1091 .Dl camcontrol tur da0
1093 Send the SCSI test unit ready command to da0.
1096 utility will report whether the disk is ready, but will not display sense
1097 information if the command fails since the
1099 switch was not specified.
1100 .Bd -literal -offset indent
1101 camcontrol tur da1 -E -C 4 -t 50 -v
1104 Send a test unit ready command to da1.
1105 Enable kernel error recovery.
1106 Specify a retry count of 4, and a timeout of 50 seconds.
1110 flag) if the command fails.
1111 Since error recovery is turned on, the
1112 disk will be spun up if it is not currently spinning.
1115 utility will report whether the disk is ready.
1116 .Bd -literal -offset indent
1117 camcontrol cmd -n cd -u 1 -v -c "3C 00 00 00 00 00 00 00 0e 00" \e
1118 -i 0xe "s1 i3 i1 i1 i1 i1 i1 i1 i1 i1 i1 i1"
1121 Issue a READ BUFFER command (0x3C) to cd1.
1122 Display the buffer size of cd1,
1123 and display the first 10 bytes from the cache on cd1.
1125 information if the command fails.
1126 .Bd -literal -offset indent
1127 camcontrol cmd -n cd -u 1 -v -c "3B 00 00 00 00 00 00 00 0e 00" \e
1128 -o 14 "00 00 00 00 1 2 3 4 5 6 v v v v" 7 8 9 8
1131 Issue a WRITE BUFFER (0x3B) command to cd1.
1132 Write out 10 bytes of data,
1133 not including the (reserved) 4 byte header.
1134 Print out sense information if
1136 Be very careful with this command, improper use may
1137 cause data corruption.
1138 .Bd -literal -offset indent
1139 camcontrol modepage da3 -m 1 -e -P 3
1142 Edit mode page 1 (the Read-Write Error Recover page) for da3, and save the
1143 settings on the drive.
1144 Mode page 1 contains a disk drive's auto read and
1145 write reallocation settings, among other things.
1147 .Dl camcontrol rescan all
1149 Rescan all SCSI busses in the system for devices that have been added,
1152 .Dl camcontrol rescan 0
1154 Rescan SCSI bus 0 for devices that have been added, removed or changed.
1156 .Dl camcontrol rescan 0:1:0
1158 Rescan SCSI bus 0, target 1, lun 0 to see if it has been added, removed, or
1161 .Dl camcontrol tags da5 -N 24
1163 Set the number of concurrent transactions for da5 to 24.
1164 .Bd -literal -offset indent
1165 camcontrol negotiate -n da -u 4 -T disable
1168 Disable tagged queueing for da4.
1169 .Bd -literal -offset indent
1170 camcontrol negotiate -n da -u 3 -R 20.000 -O 15 -a
1173 Negotiate a sync rate of 20MHz and an offset of 15 with da3.
1175 Test Unit Ready command to make the settings take effect.
1177 .Bd -literal -offset indent
1178 camcontrol smpcmd ses0 -v -r 4 "40 0 00 0" -R 1020 "s9 i1"
1181 Send the SMP REPORT GENERAL command to ses0, and display the number of PHYs
1183 Display SMP errors if the command fails.
1186 .Xr cam_cdbparse 3 ,
1193 utility first appeared in
1196 The mode page editing code and arbitrary SCSI command code are based upon
1201 library, written by Julian Elischer and Peter Dufault.
1204 program first appeared in
1206 and first appeared in
1211 .An Kenneth Merry Aq ken@FreeBSD.org
1213 The code that parses the generic command line arguments does not know that
1214 some of the subcommands take multiple arguments.
1215 So if, for instance, you
1216 tried something like this:
1217 .Bd -literal -offset indent
1218 camcontrol cmd -n da -u 1 -c "00 00 00 00 00 v" 0x00 -v
1221 The sense information from the test unit ready command would not get
1222 printed out, since the first
1226 bails out when it sees the second argument to
1230 Fixing this behavior would take some gross code, or changes to the
1233 The best way to circumvent this problem is to always make sure
1236 arguments before any command-specific arguments.
projects / FreeBSD / releng / 9.0.git / blob