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