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