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
200 .Op Fl p Ar targ_port
206 .Aq Fl p Ar targ_port
219 .Aq Fl a | Fl c Ar connection-id | Fl i Ar name | Fl p Ar portal
222 .Aq Fl a | Fl c Ar connection-id | Fl i Ar name | Fl p Ar portal
228 utility is designed to provide a way to access and control the CAM Target
230 It provides a way to send
232 commands to the CTL layer, and also provides
233 some meta-commands that utilize
238 command is implemented using the
240 REPORT LUNS and INQUIRY commands.)
244 utility has a number of primary functions, many of which require a device
246 The device identifier takes the following form:
249 Specify the target (almost always 0) and LUN number to operate on.
251 Many of the primary functions of the
253 utility take the following optional arguments:
256 Specify the number of times to retry a command in the event of failure.
258 Specify the device to open. This allows opening a device other than the
261 to be opened for sending commands.
263 Specify the initiator number to use.
266 will use 7 as the initiator number.
274 TEST UNIT READY command to the device and report whether or not it is
279 INQUIRY command to the device and display some of the returned inquiry
284 REQUEST SENSE command to the device and display the returned sense
289 REPORT LUNS command to the device and display supported LUNs.
293 READ command to the device, and write the requested data to a file or
297 Specify the starting Logical Block Address for the READ. This can be
298 specified in decimal, octal (starting with 0), hexadecimal (starting with
299 0x) or any other base supported by
302 Specify the length, in 512 byte blocks, of the READ request.
304 Specify the destination for the data read by the READ command. Either a
307 for stdout may be specified.
311 CDB (Command Data Block) size to be used for the READ request. Allowable
312 values are 6, 10, 12 and 16. Depending upon the LBA and amount of data
313 requested, a larger CDB size may be used to satisfy the request. (e.g.,
314 for LBAs above 0xffffffff, READ(16) must be used to satisfy the request.)
315 .It Fl b Ar blocksize
316 Specify the blocksize of the underlying
318 device, so the transfer length
319 can be calculated accurately. The blocksize can be obtained via the
321 READ CAPACITY command.
325 from the kernel when doing a read, just execute the command without copying
327 This is to be used for performance testing.
330 Read data from a file or stdin, and write the data to the device using the
335 Specify the starting Logical Block Address for the WRITE. This can be
336 specified in decimal, octal (starting with 0), hexadecimal (starting with
337 0x) or any other base supported by
340 Specify the length, in 512 byte blocks, of the WRITE request.
342 Specify the source for the data to be written by the WRITE command. Either a
345 for stdin may be specified.
349 CDB (Command Data Block) size to be used for the READ request. Allowable
350 values are 6, 10, 12 and 16. Depending upon the LBA and amount of data
351 requested, a larger CDB size may be used to satisfy the request. (e.g.,
352 for LBAs above 0xffffffff, READ(16) must be used to satisfy the request.)
353 .It Fl b Ar blocksize
354 Specify the blocksize of the underlying
356 device, so the transfer length
357 can be calculated accurately. The blocksize can be obtained via the
359 READ CAPACITY command.
363 to the kernel when doing a write, just execute the command without copying
365 This is to be used for performance testing.
368 Issue a SCSI READ command to the logical device to potentially force a bad
369 block on a disk in the RAID set to be reconstructed from the other disks in
370 the array. This command should only be used on an array that is in the
371 normal state. If used on a critical array, it could cause the array to go
372 offline if the bad block to be remapped is on one of the disks that is
373 still active in the array.
375 The data for this particular command will be discarded, and not returned to
378 In order to determine which LUN to read from, the user should first
379 determine which LUN the disk with a bad block belongs to. Then he should
380 map the bad disk block back to the logical block address for the array in
381 order to determine which LBA to pass in to the
385 This command is primarily intended for testing. In practice, bad block
386 remapping will generally be triggered by the in-kernel Disk Aerobics and
390 Specify the starting Logical Block Address.
392 Specify the amount of data in bytes to read from the LUN. This must be a
393 multiple of the LUN blocksize.
398 READ CAPACITY command to the device and display the device size and device
399 block size. By default, READ CAPACITY(10) is
400 used. If the device returns a maximum LBA of 0xffffffff, however,
402 will automatically issue a READ CAPACITY(16), which is implemented as a
403 service action of the SERVICE ACTION IN(16) opcode. The user can specify
404 the minimum CDB size with the
406 argument. Valid values for the
408 option are 10 and 16. If a 10 byte CDB is specified, the request will be
409 automatically reissued with a 16 byte CDB if the maximum LBA returned is
414 MODE SENSE command to the device, and display the requested mode page(s) or
418 Specify the mode page to display. This option and the
420 option are mutually exclusive. One of the two must be specified, though.
421 Mode page numbers may be specified in decimal or hexadecimal.
423 Request that the list of mode pages supported by the device be returned.
426 option are mutually exclusive. One of the two must be specified, though.
428 Specify the mode page control value. Possible values are:
429 .Bl -tag -width 2n -compact
433 Changeable value bitmask.
440 Disable block descriptors when sending the mode sense request.
442 Specify the subpage used with the mode sense request.
444 Specify the CDB size used for the mode sense request. Supported values are
450 START STOP UNIT command to the specified LUN with the start
454 Set the immediate bit in the CDB. Note that CTL does not support the
455 immediate bit, so this is primarily useful for making sure that CTL returns
458 Set the Copan proprietary on/offline bit in the CDB. When this flag is
459 used, the LUN will be marked online again (see the description of the
463 commands). When this flag is used with a
464 start command, the LUN will NOT be spun up. You need to use a start
467 flag to spin up the disks in the LUN.
472 START STOP UNIT command to the specified LUN with the start
473 bit cleared. We use an ordered tag to stop the LUN, so we can guarantee
474 that all pending I/O executes before it is stopped. (CTL guarantees this
477 sends an ordered tag for completeness.)
480 Set the immediate bit in the CDB. Note that CTL does not support the
481 immediate bit, so this is primarily useful for making sure that CTL returns
484 Set the Copan proprietary on/offline bit in the CDB. When this flag is
485 used, the LUN will be spun down and taken offline ("Logical unit not ready,
486 manual intervention required"). See the description of the
495 SYNCHRONIZE CACHE command to the device. By default, SYNCHRONIZE
496 CACHE(10) is used. If the specified starting LBA is greater than
497 0xffffffff or the length is greater than 0xffff, though,
498 SYNCHRONIZE CACHE(16) will be used. The 16 byte command will also be used
499 if the user specifies a 16 byte CDB with the
504 Specify the starting LBA of the cache region to synchronize. This option is a
505 no-op for CTL. If you send a SYNCHRONIZE CACHE command, it will sync the
506 cache for the entire LUN.
507 .It Fl b Ar blockcount
508 Specify the length of the cache region to synchronize. This option is a
509 no-op for CTL. If you send a SYNCHRONIZE CACHE command, it will sync the
510 cache for the entire LUN.
512 Specify relative addressing for the starting LBA. CTL does not support
513 relative addressing, since it only works for linked commands, and CTL
514 does not support linked commands.
516 Tell the target to return status immediately after issuing the SYNCHRONIZE CACHE
517 command rather than waiting for the cache to finish syncing. CTL does not
520 Specify the minimum CDB size. Valid values are 10 and 16 bytes.
525 START STOP UNIT command with the start bit cleared and the on/offline bit
526 set to all direct access LUNs. This will spin down all direct access LUNs,
527 and mark them offline ("Logical unit not ready, manual intervention
528 required"). Once marked offline, the state can only be cleared by sending
529 a START STOP UNIT command with the start bit set and the on/offline bit
536 will accomplish this. Note that the
537 on/offline bit is a non-standard Copan extension to the
539 START STOP UNIT command, so merely sending a normal start command from an
540 initiator will not clear the condition. (This is by design.)
544 START STOP UNIT command with the start bit set and the on/offline bit set
545 to all direct access LUNs. This will mark all direct access LUNs "online"
546 again. It will not cause any LUNs to start up. A separate start command
547 without the on/offline bit set is necessary for that.
549 Use the kernel facility for stopping all direct access LUNs and setting the
550 offline bit. Unlike the
552 command above, this command allows shutting down LUNs with I/O active. It
553 will also issue a LUN reset to any reserved LUNs to break the reservation
554 so that the LUN can be stopped.
558 This command is functionally identical to the
560 command described above. The primary difference is that the LUNs are
561 enumerated and commands sent by the in-kernel Front End Target Driver
565 List all LUNs registered with CTL.
566 Because this command uses the ioctl port, it will only work when the FETDs
567 (Front End Target Drivers) are enabled.
568 This command is the equivalent of doing a REPORT LUNS on one LUN and then
569 an INQUIRY on each LUN in the system.
571 Delay commands at the given location. There are two places where commands
572 may be delayed currently: before data is transferred
574 and just prior to sending status to the host
576 One of the two must be supplied as an argument to the
580 option must also be specified.
583 Delay command(s) at the specified location.
584 This can either be at the data movement stage (datamove) or prior to
585 command completion (done).
586 .It Fl t Ar delaytime
587 Delay command(s) for the specified number of seconds. This must be
588 specified. If set to 0, it will clear out any previously set delay for
589 this particular location (datamove or done).
590 .It Fl T Ar delaytype
591 Specify the delay type.
594 option will delay the next command sent to the given LUN.
597 option, every command will be delayed by the specified period of time.
600 the next command sent to the given LUN will be delayed and all subsequent
601 commands will be completed normally.
605 Query and control CTL's SYNCHRONIZE CACHE behavior. The
608 will show whether SYNCHRONIZE CACHE commands are being sent to the backend
610 The default is to send SYNCHRONIZE CACHE commands to the backend.
613 argument will cause all SYNCHRONIZE CACHE commands sent to all LUNs to be
617 argument will cause all SYNCHRONIZE CACHE commands sent to all LUNs to be
618 immediately returned to the initiator with successful status.
620 For a given lun, only actually service every Nth SYNCHRONIZE CACHE command
621 that is sent. This can be used for debugging the optimal time period for
622 sending SYNCHRONIZE cache commands. An interval of 0 means that the cache
623 will be flushed for this LUN every time a SYNCHRONIZE CACHE command is
626 You must specify the target and LUN you want to modify.
628 Get the interval at which we actually service the SYNCHRONIZE CACHE
629 command, as set by the
632 The reported number means that we will actually flush the cache on every
633 Nth SYNCHRONIZE CACHE command. A value of 0 means that we will flush the
636 You must specify the target and LUN you want to query.
638 Inject the specified type of error for the LUN specified, when a command
639 that matches the given pattern is seen.
640 The sense data returned is in either fixed or descriptor format, depending
641 upon the status of the D_SENSE bit in the control mode page (page 0xa) for
644 Errors are only injected for commands that have not already failed for
646 By default, only the first command matching the pattern specified is
647 returned with the supplied error.
651 flag is specified, all commands matching the pattern will be returned with
652 the specified error until the error injection command is deleted with
657 Specify the error to return:
660 Return the next matching command on the specified LUN with the sense key
661 ABORTED COMMAND (0x0b), and the ASC/ASCQ 0x45,0x00 ("Select or reselect
664 Return the next matching command on the specified LUN with the sense key
665 MEDIUM ERROR (0x03) and the ASC/ASCQ 0x11,0x00 ("Unrecovered read error") for
666 reads, or ASC/ASCQ 0x0c,0x02 ("Write error - auto reallocation failed")
669 Return the next matching command on the specified LUN with the sense key
670 UNIT ATTENTION (0x06) and the ASC/ASCQ 0x29,0x00 ("POWER ON, RESET, OR BUS
671 DEVICE RESET OCCURRED").
673 Return the next matching command on the specified LUN with the supplied
677 argument must be specified.
680 Specify which commands should be returned with the given error.
683 The error should apply to READ(6), READ(10), READ(12), READ(16), etc.
685 The error should apply to WRITE(6), WRITE(10), WRITE(12), WRITE(16), WRITE
688 The error should apply to both read and write type commands.
690 The error should apply to READ CAPACITY(10) and READ CAPACITY(16) commands.
692 The error should apply to TEST UNIT READY commands.
694 The error should apply to any command.
697 Specify the starting lba and length of the range of LBAs which should
699 This option is only applies when read and/or write patterns are specified.
700 If used with other command types, the error will never be triggered.
701 .It Fl s Ar len fmt Op Ar args
702 Specify the sense data that is to be returned for custom actions.
705 len bytes of sense data will be read from standard input and written to the
707 If len is longer than 252 bytes (the maximum allowable
709 sense data length), it will be truncated to that length.
710 The sense data format is described in
713 The error injection should be persistent, instead of happening once.
714 Persistent errors must be deleted with the
717 .It Fl d Ar delete_id
718 Delete the specified error injection serial number.
719 The serial number is returned when the error is injected.
722 Perform one of several CTL frontend port operations.
723 Either get a list of frontend ports
725 turn one or more frontends on
728 or set the World Wide Node Name
730 or World Wide Port Name
741 The WWNN and WWPN may both be specified at the same time, but cannot be
742 combined with enabling/disabling or listing ports.
745 List all CTL frontend ports or a specific port type or number.
747 Turn the specified CTL frontend ports off or on.
748 If no port number or port type is specified, all ports are turned on or
750 .It Fl p Ar targ_port
751 Specify the frontend port number.
752 The port numbers can be found in the frontend port list.
754 Omit the header in the port list output.
756 Specify the frontend type.
757 Currently defined port types are
763 (CTL ioctl interface),
768 Set the World Wide Node Name for the given port.
771 argument must be specified, since this is only possible to implement on a
773 As a general rule, the WWNN should be the same across all ports on the
776 Set the World Wide Port Name for the given port.
779 argument must be specified, since this is only possible to implement on a
781 As a general rule, the WWPN must be different for every port in the system.
783 Output the port list in XML format.
786 List CTL frontend ports.
789 Specify the frontend type.
791 Report target and connected initiators addresses.
794 .It Fl p Ar targ_port
795 Specify the frontend port number.
797 Omit the header in the port list output.
799 Enable verbose output (report all port options).
801 Output the port list in XML format.
804 Change LUN mapping for specified port.
809 are specified -- LUN will be mapped.
814 is not -- LUN will be unmapped.
819 are specified -- LUN mapping will be disabled, exposing all CTL LUNs.
821 .It Fl p Ar targ_port
822 Specify the frontend port number.
824 LUN number visible by specified port.
829 Dump the OOA (Order Of Arrival) queue for each LUN registered with CTL.
831 Dump the CTL structures to the console.
834 The backend must be specified, and depending upon the backend requested,
835 some of the other options may be required.
836 If the LUN is created successfully, the LUN configuration will be
838 If LUN creation fails, a message will be displayed describing the failure.
844 This specifies the name backend to use when creating the LUN.
849 .It Fl B Ar blocksize
850 Specify the blocksize of the backend in bytes.
851 .It Fl d Ar device_id
852 Specify the LUN-associated string to use in the
854 INQUIRY VPD page 0x83 data.
856 Request that a particular LUN number be assigned.
857 If the requested LUN number is not available, the request will fail.
858 .It Fl o Ar name=value
859 Specify a backend-specific name/value pair.
862 arguments may be specified.
863 Refer to the backend documentation for arguments that may be used.
864 .It Fl s Ar size_bytes
865 Specify the size of the LUN in bytes.
866 Some backends may allow setting the size (e.g. the ramdisk backend) and for
867 others the size may be implicit (e.g. the block backend).
868 .It Fl S Ar serial_num
869 Specify the serial number to be used in the
871 INQUIRY VPD page 0x80 data.
872 .It Fl t Ar device_type
873 Specify the numeric SCSI device type to use when creating the LUN.
874 For example, the Direct Access type is 0.
875 If this flag is not used, the type of LUN created is backend-specific.
876 Not all LUN types are supported.
877 Currently CTL only supports Direct Access (type 0) and Processor (type 3)
879 The backend requested may or may not support all of the LUN types that CTL
884 The backend must be specified, and the LUN number must also be specified.
885 Backend-specific options may also be specified with the
890 Specify the backend that owns the LUN to be removed.
896 Specify the LUN number to remove.
897 .It Fl o Ar name=value
898 Specify a backend-specific name/value pair.
901 arguments may be specified.
902 Refer to the backend documentation for arguments that may be used.
906 The backend, the LUN number, and the size must be specified.
909 Specify the backend that owns the LUN to be removed.
915 Specify the LUN number to remove.
916 .It Fl s Ar size_bytes
917 Specify the size of the LUN in bytes.
922 keyword may be passed instead; this will make CTL use the size of backing
926 Get a list of all configured LUNs.
927 This also includes the LUN size and blocksize, serial number and device ID.
931 This restricts the LUN list to the named backend.
938 This will also display any backend-specific LUN attributes in addition to
939 the standard per-LUN information.
942 The LUN list information from the kernel comes in XML format, and this
943 option allows the display of the raw XML data.
948 options are mutually exclusive.
951 the entire LUN database is displayed in XML format.
954 Get a list of currently running iSCSI connections.
955 This includes initiator and target names and the unique connection IDs.
961 The connections list information from the kernel comes in XML format, and this
962 option allows the display of the raw XML data.
965 Ask the initiator to log out iSCSI connections matching criteria.
968 Log out all connections.
970 Specify connection ID.
972 Specify initiator name.
974 Specify initiator portal (hostname or IP address).
977 Forcibly terminate iSCSI connections matching criteria.
980 Terminate all connections.
982 Specify connection ID.
984 Specify initiator name.
986 Specify initiator portal (hostname or IP address).
994 Number of additional configuration options may be specified for LUNs.
995 Some options are global, others are backend-specific.
1000 Specifies LUN vendor string up to 8 chars.
1002 Specifies LUN product string up to 16 chars.
1004 Specifies LUN revision string up to 4 chars.
1006 Specifies LUN SCSI name string.
1008 Specifies LUN EUI-64 identifier.
1010 Specifies LUN NAA identifier.
1011 Either EUI or NAA identifier should be set to UNIQUE value to allow
1012 EXTENDED COPY command access the LUN.
1013 Non-unique LUN identifiers may lead to data corruption.
1015 Setting to "on" allows EXTENDED COPY command sent to this LUN access
1016 other LUNs on this host, not accessible otherwise.
1017 This allows to offload copying between different iSCSI targets residing
1018 on the same host in trusted environments.
1020 Set to "off", disables read caching for the LUN, if supported by the backend.
1022 Set to "on", blocks all media write operations to the LUN, reporting it
1025 Set to "unrestricted", allows target to process commands with SIMPLE task
1026 attribute in arbitrary order. Any data integrity exposures related to
1027 command sequence order shall be explicitly handled by the application
1028 client through the selection of appropriate commands and task attributes.
1029 The default value is "restricted". It improves data integrity, but may
1030 introduce some additional delays.
1032 Set to "on" to serialize conseсutive reads/writes.
1033 Set to "read" to serialize conseсutive reads.
1034 Set to "off" to allow them be issued in parallel.
1035 Parallel issue of consecutive operations may confuse logic of the
1036 backing file system, hurting performance; but it may improve performance
1037 of backing stores without prefetch/write-back.
1040 Specify physical block size and offset of the device.
1043 Specify UNMAP block size and offset of the device.
1046 Specifies medium rotation rate of the device: 0 -- not reported,
1047 1 -- non-rotating (SSD), >1024 -- value in revolutions per minute.
1049 Specifies nominal form factor of the device: 0 -- not reported, 1 -- 5.25",
1050 2 -- 3.5", 3 -- 2.5", 4 -- 1.8", 5 -- less then 1.8".
1052 Set to "on", enables UNMAP support for the LUN, if supported by the backend.
1053 .It Va avail-threshold
1054 .It Va used-threshold
1055 .It Va pool-avail-threshold
1056 .It Va pool-used-threshold
1057 Set per-LUN/-pool thin provisioning soft thresholds.
1058 LUN will establish UNIT ATTENTION condition if its or pool available space
1059 get below configured avail values, or its or pool used space get above
1060 configured used values.
1061 Pool thresholds are working only for ZVOL-backed LUNs.
1063 Set to "off", disables write caching for the LUN, if supported by the backend.
1066 Options specific for block backend:
1069 Specifies file or device name to use for backing store.
1071 Specifies number of backend threads to use for this LUN.
1078 TEST UNIT READY command to LUN 1.
1080 .Dl ctladm modesense 0:1 -l
1082 Display the list of mode pages supported by LUN 1.
1084 .Dl ctladm modesense 0:0 -m 10 -P 3 -d -c 10
1086 Display the saved version of the Control mode page (page 10) on LUN 0.
1087 Disable fetching block descriptors, and use a 10 byte MODE SENSE command
1088 instead of the default 6 byte command.
1090 ctladm read 0:2 -l 0 -d 1 -b 512 -f - > foo
1093 Read the first 512 byte block from LUN 2 and dump it to the file
1096 ctladm write 0:3 -l 0xff432140 -d 20 -b 512 -f /tmp/bar
1099 Read 10240 bytes from the file
1101 and write it to target 0, LUN 3.
1102 starting at LBA 0xff432140.
1104 .Dl ctladm create -b ramdisk -s 10485760000000000
1106 Create a LUN with the
1108 ramdisk as a backing store.
1109 The LUN will claim to have a size of approximately 10 terabytes.
1111 .Dl ctladm create -b block -o file=src/usr.sbin/ctladm/ctladm.8
1113 Create a LUN using the block backend, and specify the file
1114 .Pa src/usr.sbin/ctladm/ctladm.8
1115 as the backing store.
1116 The size of the LUN will be derived from the size of the file.
1118 .Dl ctladm create -b block -o file=src/usr.sbin/ctladm/ctladm.8 -S MYSERIAL321 -d MYDEVID123
1120 Create a LUN using the block backend, specify the file
1121 .Pa src/usr.sbin/ctladm/ctladm.8
1122 as the backing store, and specify the
1124 VPD page 0x80 and 0x83 serial number
1129 .Dl ctladm remove -b block -l 12
1131 Remove LUN 12, which is handled by the block backend, from the system.
1135 List configured LUNs in the system, along with their backend and serial
1137 This works when the Front End Target Drivers are enabled or disabled.
1141 List all LUNs in the system, along with their inquiry data and device type.
1142 This only works when the FETDs are enabled, since the commands go through the
1145 .Dl ctladm inject 0:6 -i mediumerr -p read -r 0,512 -c
1147 Inject a medium error on LUN 6 for every read that covers the first 512
1149 .Bd -literal -offset indent
1150 ctladm inject 0:6 -i custom -p tur -s 18 "f0 0 02 s12 04 02"
1153 Inject a custom error on LUN 6 for the next TEST UNIT READY command only.
1154 This will result in a sense key of NOT READY (0x02), and an ASC/ASCQ of
1155 0x04,0x02 ("Logical unit not ready, initializing command required").
1158 .Xr cam_cdbparse 3 ,
1168 utility was originally written during the Winter/Spring of 2003 as an
1171 .An Ken Merry Aq ken@FreeBSD.org
projects / FreeBSD / releng / 10.2.git / blob