3 vdev_id.conf \- Configuration file for vdev_id
6 is the configuration file for
8 It controls the default behavior of
10 while it is mapping a disk device name to an alias.
14 file uses a simple format consisting of a keyword followed by one or
15 more values on a single line. Any line not beginning with a recognized
16 keyword is ignored. Comments may optionally begin with a hash
19 The following keywords and values are used.
21 \fIalias\fR <name> <devlink>
22 Maps a device link in the /dev directory hierarchy to a new device
23 name. The udev rule defining the device link must have run prior to
25 A defined alias takes precedence over a topology-derived name, but the
26 two naming methods can otherwise coexist. For example, one might name
27 drives in a JBOD with the sas_direct topology while naming an internal
28 L2ARC device with an alias.
30 \fIname\fR - the name of the link to the device that will by created in
33 \fIdevlink\fR - the name of the device link that has already been
34 defined by udev. This may be an absolute path or the base filename.
37 \fIchannel\fR [pci_slot] <port> <name>
38 Maps a physical path to a channel name (typically representing a single
41 \fIpci_slot\fR - specifies the PCI SLOT of the HBA
42 hosting the disk enclosure being mapped, as found in the output of
44 This argument is not used in sas_switch mode.
46 \fIport\fR - specifies the numeric identifier of the HBA or SAS switch port
47 connected to the disk enclosure being mapped.
49 \fIname\fR - specifies the name of the channel.
52 \fIslot\fR <old> <new> [channel]
53 Maps a disk slot number as reported by the operating system to an
54 alternative slot number. If the \fIchannel\fR parameter is specified
55 then the mapping is only applied to slots in the named channel,
56 otherwise the mapping is applied to all channels. The first-specified
57 \fIslot\fR rule that can match a slot takes precedence. Therefore a
58 channel-specific mapping for a given slot should generally appear before
59 a generic mapping for the same slot. In this way a custom mapping may
60 be applied to a particular channel and a default mapping applied to the
64 \fImultipath\fR <yes|no>
67 will handle only dm-multipath devices. If set to "yes" then
69 will examine the first running component disk of a dm-multipath
70 device as listed by the
72 command to determine the physical path.
74 \fItopology\fR <sas_direct|sas_switch>
75 Identifies a physical topology that governs how physical paths are
78 \fIsas_direct\fR - in this mode a channel is uniquely identified by
79 a PCI slot and a HBA port number
81 \fIsas_switch\fR - in this mode a channel is uniquely identified by
82 a SAS switch port number
85 \fIphys_per_port\fR <num>
86 Specifies the number of PHY devices associated with a SAS HBA port or SAS
89 internally uses this value to determine which HBA or switch port a
90 device is connected to. The default is 4.
92 A non-multipath configuration with direct-attached SAS enclosures and an
93 arbitrary slot re-mapping.
100 # PCI_SLOT HBA PORT CHANNEL NAME
106 # Custom mapping for Channel A
115 # Default mapping for B, C, and D
123 A SAS-switch topology. Note that the
125 keyword takes only two arguments in this example.
130 # SWITCH PORT CHANNEL NAME
137 A multipath configuration. Note that channel names have multiple
138 definitions - one per physical path.
143 # PCI_SLOT HBA PORT CHANNEL NAME
150 A configuration using device link aliases.
154 # name fully qualified or base name of device link
155 alias d1 /dev/disk/by-id/wwn-0x5000c5002de3b9ca
156 alias d2 wwn-0x5000c5002def789e
162 .I /etc/zfs/vdev_id.conf
163 The configuration file for