2 .\" Copyright (c) 2003 Silicon Graphics International Corp.
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 .\" without modification.
11 .\" 2. Redistributions in binary form must reproduce at minimum a disclaimer
12 .\" substantially similar to the "NO WARRANTY" disclaimer below
13 .\" ("Disclaimer") and any redistribution must be conditioned upon
14 .\" including a substantially similar Disclaimer requirement for further
15 .\" binary redistribution.
18 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
19 .\" "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
20 .\" LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR
21 .\" A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
22 .\" HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
26 .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
27 .\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
28 .\" POSSIBILITY OF SUCH DAMAGES.
30 .\" ctladm utility man page.
32 .\" Author: Ken Merry <ken@FreeBSD.org>
34 .\" $Id: //depot/users/kenm/FreeBSD-test2/usr.sbin/ctladm/ctladm.8#3 $
42 .Nd CAM Target Layer control utility
72 .Aq Fl b Ar blocksize_bytes
82 .Aq Fl b Ar blocksize_bytes
99 .Aq Fl m Ar page | Fl l
121 .Op Fl b Ar blockcount
140 .Aq Fl l Ar datamove|done
142 .Op Fl T Ar oneshot|cont
144 .Ic realsync Aq on|off|query
157 .Op Fl s Ar len fmt Op Ar args
159 .Op Fl d Ar delete_id
163 .Op Fl B Ar blocksize
164 .Op Fl d Ar device_id
166 .Op Fl o Ar name=value
167 .Op Fl s Ar size_bytes
168 .Op Fl S Ar serial_num
169 .Op Fl t Ar device_type
174 .Op Fl o Ar name=value
179 .Aq Fl s Ar size_bytes
191 .Op Fl p Ar targ_port
199 .Op Fl p Ar targ_port
213 .Aq Fl a | Fl c Ar connection-id | Fl i Ar name | Fl p Ar portal
216 .Aq Fl a | Fl c Ar connection-id | Fl i Ar name | Fl p Ar portal
222 utility is designed to provide a way to access and control the CAM Target
224 It provides a way to send
226 commands to the CTL layer, and also provides
227 some meta-commands that utilize
232 command is implemented using the
234 REPORT LUNS and INQUIRY commands.)
238 utility has a number of primary functions, many of which require a device
240 The device identifier takes the following form:
243 Specify the target (almost always 0) and LUN number to operate on.
245 Many of the primary functions of the
247 utility take the following optional arguments:
250 Specify the number of times to retry a command in the event of failure.
252 Specify the device to open. This allows opening a device other than the
255 to be opened for sending commands.
257 Specify the initiator number to use.
260 will use 7 as the initiator number.
268 TEST UNIT READY command to the device and report whether or not it is
273 INQUIRY command to the device and display some of the returned inquiry
278 REQUEST SENSE command to the device and display the returned sense
283 REPORT LUNS command to the device and display supported LUNs.
287 READ command to the device, and write the requested data to a file or
291 Specify the starting Logical Block Address for the READ. This can be
292 specified in decimal, octal (starting with 0), hexadecimal (starting with
293 0x) or any other base supported by
296 Specify the length, in 512 byte blocks, of the READ request.
298 Specify the destination for the data read by the READ command. Either a
301 for stdout may be specified.
305 CDB (Command Data Block) size to be used for the READ request. Allowable
306 values are 6, 10, 12 and 16. Depending upon the LBA and amount of data
307 requested, a larger CDB size may be used to satisfy the request. (e.g.,
308 for LBAs above 0xffffffff, READ(16) must be used to satisfy the request.)
309 .It Fl b Ar blocksize
310 Specify the blocksize of the underlying
312 device, so the transfer length
313 can be calculated accurately. The blocksize can be obtained via the
315 READ CAPACITY command.
319 from the kernel when doing a read, just execute the command without copying
321 This is to be used for performance testing.
324 Read data from a file or stdin, and write the data to the device using the
329 Specify the starting Logical Block Address for the WRITE. This can be
330 specified in decimal, octal (starting with 0), hexadecimal (starting with
331 0x) or any other base supported by
334 Specify the length, in 512 byte blocks, of the WRITE request.
336 Specify the source for the data to be written by the WRITE command. Either a
339 for stdin may be specified.
343 CDB (Command Data Block) size to be used for the READ request. Allowable
344 values are 6, 10, 12 and 16. Depending upon the LBA and amount of data
345 requested, a larger CDB size may be used to satisfy the request. (e.g.,
346 for LBAs above 0xffffffff, READ(16) must be used to satisfy the request.)
347 .It Fl b Ar blocksize
348 Specify the blocksize of the underlying
350 device, so the transfer length
351 can be calculated accurately. The blocksize can be obtained via the
353 READ CAPACITY command.
357 to the kernel when doing a write, just execute the command without copying
359 This is to be used for performance testing.
362 Issue a SCSI READ command to the logical device to potentially force a bad
363 block on a disk in the RAID set to be reconstructed from the other disks in
364 the array. This command should only be used on an array that is in the
365 normal state. If used on a critical array, it could cause the array to go
366 offline if the bad block to be remapped is on one of the disks that is
367 still active in the array.
369 The data for this particular command will be discarded, and not returned to
372 In order to determine which LUN to read from, the user should first
373 determine which LUN the disk with a bad block belongs to. Then he should
374 map the bad disk block back to the logical block address for the array in
375 order to determine which LBA to pass in to the
379 This command is primarily intended for testing. In practice, bad block
380 remapping will generally be triggered by the in-kernel Disk Aerobics and
384 Specify the starting Logical Block Address.
386 Specify the amount of data in bytes to read from the LUN. This must be a
387 multiple of the LUN blocksize.
392 READ CAPACITY command to the device and display the device size and device
393 block size. By default, READ CAPACITY(10) is
394 used. If the device returns a maximum LBA of 0xffffffff, however,
396 will automatically issue a READ CAPACITY(16), which is implemented as a
397 service action of the SERVICE ACTION IN(16) opcode. The user can specify
398 the minimum CDB size with the
400 argument. Valid values for the
402 option are 10 and 16. If a 10 byte CDB is specified, the request will be
403 automatically reissued with a 16 byte CDB if the maximum LBA returned is
408 MODE SENSE command to the device, and display the requested mode page(s) or
412 Specify the mode page to display. This option and the
414 option are mutually exclusive. One of the two must be specified, though.
415 Mode page numbers may be specified in decimal or hexadecimal.
417 Request that the list of mode pages supported by the device be returned.
420 option are mutually exclusive. One of the two must be specified, though.
422 Specify the mode page control value. Possible values are:
423 .Bl -tag -width 2n -compact
427 Changeable value bitmask.
434 Disable block descriptors when sending the mode sense request.
436 Specify the subpage used with the mode sense request.
438 Specify the CDB size used for the mode sense request. Supported values are
444 START STOP UNIT command to the specified LUN with the start
448 Set the immediate bit in the CDB. Note that CTL does not support the
449 immediate bit, so this is primarily useful for making sure that CTL returns
452 Set the Copan proprietary on/offline bit in the CDB. When this flag is
453 used, the LUN will be marked online again (see the description of the
457 commands). When this flag is used with a
458 start command, the LUN will NOT be spun up. You need to use a start
461 flag to spin up the disks in the LUN.
466 START STOP UNIT command to the specified LUN with the start
467 bit cleared. We use an ordered tag to stop the LUN, so we can guarantee
468 that all pending I/O executes before it is stopped. (CTL guarantees this
471 sends an ordered tag for completeness.)
474 Set the immediate bit in the CDB. Note that CTL does not support the
475 immediate bit, so this is primarily useful for making sure that CTL returns
478 Set the Copan proprietary on/offline bit in the CDB. When this flag is
479 used, the LUN will be spun down and taken offline ("Logical unit not ready,
480 manual intervention required"). See the description of the
489 SYNCHRONIZE CACHE command to the device. By default, SYNCHRONIZE
490 CACHE(10) is used. If the specified starting LBA is greater than
491 0xffffffff or the length is greater than 0xffff, though,
492 SYNCHRONIZE CACHE(16) will be used. The 16 byte command will also be used
493 if the user specifies a 16 byte CDB with the
498 Specify the starting LBA of the cache region to synchronize. This option is a
499 no-op for CTL. If you send a SYNCHRONIZE CACHE command, it will sync the
500 cache for the entire LUN.
501 .It Fl b Ar blockcount
502 Specify the length of the cache region to synchronize. This option is a
503 no-op for CTL. If you send a SYNCHRONIZE CACHE command, it will sync the
504 cache for the entire LUN.
506 Specify relative addressing for the starting LBA. CTL does not support
507 relative addressing, since it only works for linked commands, and CTL
508 does not support linked commands.
510 Tell the target to return status immediately after issuing the SYNCHRONIZE CACHE
511 command rather than waiting for the cache to finish syncing. CTL does not
514 Specify the minimum CDB size. Valid values are 10 and 16 bytes.
519 START STOP UNIT command with the start bit cleared and the on/offline bit
520 set to all direct access LUNs. This will spin down all direct access LUNs,
521 and mark them offline ("Logical unit not ready, manual intervention
522 required"). Once marked offline, the state can only be cleared by sending
523 a START STOP UNIT command with the start bit set and the on/offline bit
530 will accomplish this. Note that the
531 on/offline bit is a non-standard Copan extension to the
533 START STOP UNIT command, so merely sending a normal start command from an
534 initiator will not clear the condition. (This is by design.)
538 START STOP UNIT command with the start bit set and the on/offline bit set
539 to all direct access LUNs. This will mark all direct access LUNs "online"
540 again. It will not cause any LUNs to start up. A separate start command
541 without the on/offline bit set is necessary for that.
543 Use the kernel facility for stopping all direct access LUNs and setting the
544 offline bit. Unlike the
546 command above, this command allows shutting down LUNs with I/O active. It
547 will also issue a LUN reset to any reserved LUNs to break the reservation
548 so that the LUN can be stopped.
552 This command is functionally identical to the
554 command described above. The primary difference is that the LUNs are
555 enumerated and commands sent by the in-kernel Front End Target Driver
559 List all LUNs registered with CTL.
560 Because this command uses the ioctl port, it will only work when the FETDs
561 (Front End Target Drivers) are enabled.
562 This command is the equivalent of doing a REPORT LUNS on one LUN and then
563 an INQUIRY on each LUN in the system.
565 Delay commands at the given location. There are two places where commands
566 may be delayed currently: before data is transferred
568 and just prior to sending status to the host
570 One of the two must be supplied as an argument to the
574 option must also be specified.
577 Delay command(s) at the specified location.
578 This can either be at the data movement stage (datamove) or prior to
579 command completion (done).
580 .It Fl t Ar delaytime
581 Delay command(s) for the specified number of seconds. This must be
582 specified. If set to 0, it will clear out any previously set delay for
583 this particular location (datamove or done).
584 .It Fl T Ar delaytype
585 Specify the delay type.
588 option will delay the next command sent to the given LUN.
591 option, every command will be delayed by the specified period of time.
594 the next command sent to the given LUN will be delayed and all subsequent
595 commands will be completed normally.
599 Query and control CTL's SYNCHRONIZE CACHE behavior. The
602 will show whether SYNCHRONIZE CACHE commands are being sent to the backend
604 The default is to send SYNCHRONIZE CACHE commands to the backend.
607 argument will cause all SYNCHRONIZE CACHE commands sent to all LUNs to be
611 argument will cause all SYNCHRONIZE CACHE commands sent to all LUNs to be
612 immediately returned to the initiator with successful status.
614 For a given lun, only actually service every Nth SYNCHRONIZE CACHE command
615 that is sent. This can be used for debugging the optimal time period for
616 sending SYNCHRONIZE cache commands. An interval of 0 means that the cache
617 will be flushed for this LUN every time a SYNCHRONIZE CACHE command is
620 You must specify the target and LUN you want to modify.
622 Get the interval at which we actually service the SYNCHRONIZE CACHE
623 command, as set by the
626 The reported number means that we will actually flush the cache on every
627 Nth SYNCHRONIZE CACHE command. A value of 0 means that we will flush the
630 You must specify the target and LUN you want to query.
632 Inject the specified type of error for the LUN specified, when a command
633 that matches the given pattern is seen.
634 The sense data returned is in either fixed or descriptor format, depending
635 upon the status of the D_SENSE bit in the control mode page (page 0xa) for
638 Errors are only injected for commands that have not already failed for
640 By default, only the first command matching the pattern specified is
641 returned with the supplied error.
645 flag is specified, all commands matching the pattern will be returned with
646 the specified error until the error injection command is deleted with
651 Specify the error to return:
654 Return the next matching command on the specified LUN with the sense key
655 ABORTED COMMAND (0x0b), and the ASC/ASCQ 0x45,0x00 ("Select or reselect
658 Return the next matching command on the specified LUN with the sense key
659 MEDIUM ERROR (0x03) and the ASC/ASCQ 0x11,0x00 ("Unrecovered read error") for
660 reads, or ASC/ASCQ 0x0c,0x02 ("Write error - auto reallocation failed")
663 Return the next matching command on the specified LUN with the sense key
664 UNIT ATTENTION (0x06) and the ASC/ASCQ 0x29,0x00 ("POWER ON, RESET, OR BUS
665 DEVICE RESET OCCURRED").
667 Return the next matching command on the specified LUN with the supplied
671 argument must be specified.
674 Specify which commands should be returned with the given error.
677 The error should apply to READ(6), READ(10), READ(12), READ(16), etc.
679 The error should apply to WRITE(6), WRITE(10), WRITE(12), WRITE(16), WRITE
682 The error should apply to both read and write type commands.
684 The error should apply to READ CAPACITY(10) and READ CAPACITY(16) commands.
686 The error should apply to TEST UNIT READY commands.
688 The error should apply to any command.
691 Specify the starting lba and length of the range of LBAs which should
693 This option is only applies when read and/or write patterns are specified.
694 If used with other command types, the error will never be triggered.
695 .It Fl s Ar len fmt Op Ar args
696 Specify the sense data that is to be returned for custom actions.
699 len bytes of sense data will be read from standard input and written to the
701 If len is longer than 252 bytes (the maximum allowable
703 sense data length), it will be truncated to that length.
704 The sense data format is described in
707 The error injection should be persistent, instead of happening once.
708 Persistent errors must be deleted with the
711 .It Fl d Ar delete_id
712 Delete the specified error injection serial number.
713 The serial number is returned when the error is injected.
716 Perform one of several CTL frontend port operations.
717 Either get a list of frontend ports
719 turn one or more frontends on
722 or set the World Wide Node Name
724 or World Wide Port Name
735 The WWNN and WWPN may both be specified at the same time, but cannot be
736 combined with enabling/disabling or listing ports.
739 List all CTL frontend ports or a specific port type or number.
741 Turn the specified CTL frontend ports off or on.
742 If no port number or port type is specified, all ports are turned on or
744 .It Fl p Ar targ_port
745 Specify the frontend port number.
746 The port numbers can be found in the frontend port list.
748 Omit the header in the port list output.
750 Specify the frontend type.
751 Currently defined port types are
757 (CTL ioctl interface),
762 Set the World Wide Node Name for the given port.
765 argument must be specified, since this is only possible to implement on a
767 As a general rule, the WWNN should be the same across all ports on the
770 Set the World Wide Port Name for the given port.
773 argument must be specified, since this is only possible to implement on a
775 As a general rule, the WWPN must be different for every port in the system.
777 Output the port list in XML format.
780 List CTL frontend ports.
783 Specify the frontend type.
785 Report target and connected initiators addresses
786 .It Fl p Ar targ_port
787 Specify the frontend port number.
789 Omit the header in the port list output.
791 Enable verbose output (report all port options).
793 Output the port list in XML format.
796 Dump the OOA (Order Of Arrival) queue for each LUN registered with CTL.
798 Dump the CTL structures to the console.
801 The backend must be specified, and depending upon the backend requested,
802 some of the other options may be required.
803 If the LUN is created successfully, the LUN configuration will be
805 If LUN creation fails, a message will be displayed describing the failure.
811 This specifies the name backend to use when creating the LUN.
816 .It Fl B Ar blocksize
817 Specify the blocksize of the backend in bytes.
818 .It Fl d Ar device_id
819 Specify the LUN-associated string to use in the
821 INQUIRY VPD page 0x83 data.
823 Request that a particular LUN number be assigned.
824 If the requested LUN number is not available, the request will fail.
825 .It Fl o Ar name=value
826 Specify a backend-specific name/value pair.
829 arguments may be specified.
830 Refer to the backend documentation for arguments that may be used.
831 .It Fl s Ar size_bytes
832 Specify the size of the LUN in bytes.
833 Some backends may allow setting the size (e.g. the ramdisk backend) and for
834 others the size may be implicit (e.g. the block backend).
835 .It Fl S Ar serial_num
836 Specify the serial number to be used in the
838 INQUIRY VPD page 0x80 data.
839 .It Fl t Ar device_type
840 Specify the numeric SCSI device type to use when creating the LUN.
841 For example, the Direct Access type is 0.
842 If this flag is not used, the type of LUN created is backend-specific.
843 Not all LUN types are supported.
844 Currently CTL only supports Direct Access (type 0) and Processor (type 3)
846 The backend requested may or may not support all of the LUN types that CTL
851 The backend must be specified, and the LUN number must also be specified.
852 Backend-specific options may also be specified with the
857 Specify the backend that owns the LUN to be removed.
863 Specify the LUN number to remove.
864 .It Fl o Ar name=value
865 Specify a backend-specific name/value pair.
868 arguments may be specified.
869 Refer to the backend documentation for arguments that may be used.
873 The backend, the LUN number, and the size must be specified.
876 Specify the backend that owns the LUN to be removed.
882 Specify the LUN number to remove.
883 .It Fl s Ar size_bytes
884 Specify the size of the LUN in bytes.
889 keyword may be passed instead; this will make CTL use the size of backing
893 Get a list of all configured LUNs.
894 This also includes the LUN size and blocksize, serial number and device ID.
898 This restricts the LUN list to the named backend.
905 This will also display any backend-specific LUN attributes in addition to
906 the standard per-LUN information.
909 The LUN list information from the kernel comes in XML format, and this
910 option allows the display of the raw XML data.
915 options are mutually exclusive.
918 the entire LUN database is displayed in XML format.
921 Get a list of currently running iSCSI connections.
922 This includes initiator and target names and the unique connection IDs.
928 The connections list information from the kernel comes in XML format, and this
929 option allows the display of the raw XML data.
932 Ask the initiator to log out iSCSI connections matching criteria.
935 Log out all connections.
937 Specify connection ID.
939 Specify initiator name.
941 Specify initiator portal (hostname or IP address).
944 Forcibly terminate iSCSI connections matching criteria.
947 Terminate all connections.
949 Specify connection ID.
951 Specify initiator name.
953 Specify initiator portal (hostname or IP address).
961 Number of additional configuration options may be specified for LUNs.
962 Some options are global, others are backend-specific.
967 Specifies LUN vendor string up to 8 chars.
969 Specifies LUN product string up to 16 chars.
971 Specifies LUN revision string up to 4 chars.
973 Specifies LUN SCSI name string.
975 Specifies LUN EUI-64 identifier.
977 Specifies LUN NAA identifier.
978 Either EUI or NAA identifier should be set to UNIQUE value to allow
979 EXTENDED COPY command access the LUN.
980 Non-unique LUN identifiers may lead to data corruption.
982 Setting to "on" allows EXTENDED COPY command sent to this LUN access
983 other LUNs on this host, not accessible otherwise.
984 This allows to offload copying between different iSCSI targets residing
985 on the same host in trusted environments.
987 Set to "off", disables read caching for the LUN, if supported by the backend.
989 Set to "on", blocks all media write operations to the LUN, reporting it
992 Set to "unrestricted", allows target to process commands with SIMPLE task
993 attribute in arbitrary order. Any data integrity exposures related to
994 command sequence order shall be explicitly handled by the application
995 client through the selection of appropriate commands and task attributes.
996 The default value is "restricted". It improves data integrity, but may
997 introduce some additional delays.
999 Set to "on" to serialize conseсutive reads/writes.
1000 Set to "read" to serialize conseсutive reads.
1001 Set to "off" to allow them be issued in parallel.
1002 Parallel issue of consecutive operations may confuse logic of the
1003 backing file system, hurting performance; but it may improve performance
1004 of backing stores without prefetch/write-back.
1006 Specifies medium rotation rate of the device: 0 -- not reported,
1007 1 -- non-rotating (SSD), >1024 -- value in revolutions per minute.
1009 Specifies nominal form factor of the device: 0 -- not reported, 1 -- 5.25",
1010 2 -- 3.5", 3 -- 2.5", 4 -- 1.8", 5 -- less then 1.8".
1012 Set to "on", enables UNMAP support for the LUN, if supported by the backend.
1013 .It Va avail-threshold
1014 .It Va used-threshold
1015 .It Va pool-avail-threshold
1016 .It Va pool-used-threshold
1017 Set per-LUN/-pool thin provisioning soft thresholds.
1018 LUN will establish UNIT ATTENTION condition if its or pool available space
1019 get below configured avail values, or its or pool used space get above
1020 configured used values.
1021 Pool thresholds are working only for ZVOL-backed LUNs.
1023 Set to "off", disables write caching for the LUN, if supported by the backend.
1026 Options specific for block backend:
1029 Specifies file or device name to use for backing store.
1031 Specifies number of backend threads to use for this LUN.
1038 TEST UNIT READY command to LUN 1.
1040 .Dl ctladm modesense 0:1 -l
1042 Display the list of mode pages supported by LUN 1.
1044 .Dl ctladm modesense 0:0 -m 10 -P 3 -d -c 10
1046 Display the saved version of the Control mode page (page 10) on LUN 0.
1047 Disable fetching block descriptors, and use a 10 byte MODE SENSE command
1048 instead of the default 6 byte command.
1050 ctladm read 0:2 -l 0 -d 1 -b 512 -f - > foo
1053 Read the first 512 byte block from LUN 2 and dump it to the file
1056 ctladm write 0:3 -l 0xff432140 -d 20 -b 512 -f /tmp/bar
1059 Read 10240 bytes from the file
1061 and write it to target 0, LUN 3.
1062 starting at LBA 0xff432140.
1064 .Dl ctladm create -b ramdisk -s 10485760000000000
1066 Create a LUN with the
1068 ramdisk as a backing store.
1069 The LUN will claim to have a size of approximately 10 terabytes.
1071 .Dl ctladm create -b block -o file=src/usr.sbin/ctladm/ctladm.8
1073 Create a LUN using the block backend, and specify the file
1074 .Pa src/usr.sbin/ctladm/ctladm.8
1075 as the backing store.
1076 The size of the LUN will be derived from the size of the file.
1078 .Dl ctladm create -b block -o file=src/usr.sbin/ctladm/ctladm.8 -S MYSERIAL321 -d MYDEVID123
1080 Create a LUN using the block backend, specify the file
1081 .Pa src/usr.sbin/ctladm/ctladm.8
1082 as the backing store, and specify the
1084 VPD page 0x80 and 0x83 serial number
1089 .Dl ctladm remove -b block -l 12
1091 Remove LUN 12, which is handled by the block backend, from the system.
1095 List configured LUNs in the system, along with their backend and serial
1097 This works when the Front End Target Drivers are enabled or disabled.
1101 List all LUNs in the system, along with their inquiry data and device type.
1102 This only works when the FETDs are enabled, since the commands go through the
1105 .Dl ctladm inject 0:6 -i mediumerr -p read -r 0,512 -c
1107 Inject a medium error on LUN 6 for every read that covers the first 512
1109 .Bd -literal -offset indent
1110 ctladm inject 0:6 -i custom -p tur -s 18 "f0 0 02 s12 04 02"
1113 Inject a custom error on LUN 6 for the next TEST UNIT READY command only.
1114 This will result in a sense key of NOT READY (0x02), and an ASC/ASCQ of
1115 0x04,0x02 ("Logical unit not ready, initializing command required").
1118 .Xr cam_cdbparse 3 ,
1127 utility was originally written during the Winter/Spring of 2003 as an
1130 .An Ken Merry Aq ken@FreeBSD.org
projects / FreeBSD / stable / 10.git / blob