1 .TH SCSI_ID 8 "December 2003" "" "Linux Administrator's Manual"
3 scsi_id \- retrieve and generate a unique SCSI identifier
9 queries a SCSI device via the SCSI INQUIRY vital product data (VPD) page 0x80 or
10 0x83 and uses the resulting data to generate a value that is unique across
11 all SCSI devices that properly support page 0x80 or page 0x83.
13 If a result is generated it is sent to standard output, and the program
14 exits with a zero value. If no identifier is output, the program exits
15 with a non\-zero value.
17 \fBscsi_id\fP is primarily for use by other utilities such as \fBudev\fP
18 that require a unique SCSI identifier.
20 By default all devices are assume black listed, the \fB\-g\fP option must
21 be specified on the command line or in the config file for any useful
24 SCSI commands are sent directly to the device via the SG_IO ioctl
27 In order to generate unique values for either page 0x80 or page 0x83, the
28 serial numbers or world wide names are prefixed as follows.
30 Identifiers based on page 0x80 are prefixed by the character 'S', the SCSI
31 vendor, the SCSI product (model) and then the the serial number returned
32 by page 0x80. For example:
36 # scsi_id -p 0x80 -s /block/sdg
41 Identifiers based on page 0x83 are prefixed by the identifier type
42 followed by the page 0x83 identifier. For example, a device with a NAA
43 (Name Address Authority) type of 3 (also in this case the page 0x83
44 identifier starts with the NAA value of 6):
48 # /sbin/scsi_id -p 0x83 -s /block/sdg
49 3600a0b80000b174b000000d63efc5c8c
56 Deprecated method: when called with only a single argument without a
57 leading \-, runs in a hotplug mode, and expects the environment variable
58 DEVPATH to specify the corresponding sysfs device. See section below on
59 usage with \fBudev\fP.
62 Always print information (model, vendor strings) about the device even
63 if it does not support VPD pages.
66 The default behaviour \- treat the device as black listed, and do nothing
67 unless a white listed device is found in the scsi_id config\-file.
71 of determining and creating a device node based on a sysfs dev
72 entry as done for the \fB\-s\fP, send SG_IO commands to
73 \fBdevice\fP, such as \fB/dev/sdc\fP.
74 This argument should also be used when invoked via udev to avoid problems
75 with creation of temporary files on not-yet writable directories.
77 .BI \-f "\| config\-file"
78 Read configuration and black/white list entries from
80 rather than the default
81 .B /etc/scsi_id.config
85 Treat the device as white listed. The \fB\-g\fP option must be specified
86 on the command line or in the scsi_id configuration file for
88 to generate any output.
91 Prefix the identification string with the driver model (sysfs) bus id of
94 .BI \-p "\| 0x80 | 0x83 | pre-spc3-83"
95 Use SCSI INQUIRY VPD page code 0x80, 0x83, or pre-spc3-83.
98 behaviour is to query the availabe VPD pages, and use page 0x83 if found,
99 else page 0x80 if found, else nothing.
101 Page pre-spc3-83 should only be utilized for those scsi devices which
102 are not compliant with the SPC-2 or SPC-3 format for page 83. While this
103 option is used for older model 4, 5, and 6 EMC Symmetrix devices, its
104 use with SPC-2 or SPC-3 compliant devices will fallback to the page 83
105 format supported by these devices.
107 .BI \-s "\| sysfs\-device"
108 Generate an id for the
110 The sysfs mount point must not be included. For example, use /block/sd,
114 Reformat the output : replace all whitespaces by underscores
117 Generate verbose debugging output.
120 Display version number and exit.
125 If \fBscsi_id\fP is invoked with one argument without a leading \-, it
126 assumes it is called for a hotplug event, and looks for the sysfs device
127 in the DEVPATH environment variable. This mode is deprecated, but
128 available for backwards compatibility.
130 If the DEVPATH environment variable is set, scsi_id assumes it has been
131 invoked via udev (or some other hotplug program), and all errors or
132 warnings are sent using syslog.
134 To determine the specific value needed in a RESULT key, use the \-s option,
139 /sbin/scsi_id -s /block/sda
143 An example \fBudev\fP rule using \fBscsi_id\fP, that will name a block
144 device and any partitions for the device matching the \fBscsi_id\fP output
149 BUS="scsi", PROGRAM="/sbin/scsi_id -d %N -s %p", RESULT="312345", NAME="disk%n"
157 /etc/scsi_id.config configuration and black/white list entries
161 .BR udev (8), hotplug (8)
163 Developed by Patrick Mansfield <patmans@us.ibm.com> based on SCSI ID
164 source included in earlier linux 2.5 kernels, sg_utils source, and SCSI