Device Mapper Multipath Input Output often shortened to DM-Multipathing and abbreviated as DM-MPIO provides input-output (I/O) fail-over and load-balancing by using multipath I/O within Linux for block devices.[1][2][3] By utilizing device-mapper, the multipathd daemon provides the host-side logic to use multiple paths of a redundant network to provide continuous availability and higher-bandwidth connectivity between the host server and the block-level device.[4] DM-MPIO handles the rerouting of block I/O to an alternate path in the event of a path failure. DM-MPIO can also balance the I/O load across all of the available paths that are typically utilized in Fibre Channel (FC) and iSCSISAN environments.[5]
DM-MPIO is based on the device mapper,[6] which provides the basic framework that maps one block device onto another.
Considerations
When utilizing Linux DM-MPIO in a datacenter that has other operating systems and multipath solutions, key components of path management must be considered.
Load balancing — The workload is distributed across the available hardware components. Goal: Reduce I/O completion time, maximize throughput, and optimize resources
Path failover and recovery — Utilizes redundant I/O channels to redirect application reads and writes when one or more paths are no longer available.
History
DM-MPIO started as a patch set created by Joe Thornber, and was later maintained by Alasdair G Kergon at Red Hat. It was included in mainline Linux with kernel version 2.6.12, which was released on June 17, 2005.[7]
Components
Simple multipath example
DM-MPIO in Linux consists of kernel components and user-space components.
Kernel – device-mapper – block subsystem that provides layering mechanism for block devices.
dm-multipath – kernel module implementing the multipath device-mapper target.
User-space – multipath-tools – provides the tools to manage multipathed devices by instructing the device-mapper multipath module what to do. The tools consist of:
Multipath: scans the system for multipathed devices, assembles them, updates the device-mapper's map.[5]
Multipathd: daemon that waits for maps events, and then executes multipath and monitors the paths. Marks a path as failed when the path becomes faulty. Depending on the failback policy, it can reactivate the path.[5]
Devmap-name: provides a meaningful device-name to udev for devmaps.[5]
Kpartx: maps linear devmaps to device partitions to make multipath maps partitionable.[5]
Multipath.conf: configuration file for the multipath daemon. Used to overwrite the built-in configuration table of multipathd.
Configuration file
The configuration file /etc/multipath.conf makes many of the DM-MPIO features user-configurable. The multipath command and the kernel daemon multipathd use information found in this file. The file is only consulted during the configuration of the multipath devices. Changes must be made prior to running the multipath command. Changes to the file afterward will require multipath to be executed again.
System level defaults (defaults): User can override system level defaults.
Blacklisted devices (blacklist): User specifies the list of devices that are not to be under the control of DM-MPIO.
Blacklist exceptions (blacklist_exceptions): Specific devices to be treated as multipath devices even if listed in the blacklist.
Storage controller specific settings (devices): User specified configuration settings will be applied to devices with specified "Vendor" and "Product" information.
Device specific settings (multipaths): Fine tune the configuration settings for individual LUNs.
Terminology
HBA: Host bus adapters provide the physical interface between the input/output (I/O) host bus of Fibre Channel devices and the underlying Fibre Channel network.[9]
Path: Connection from the server through the HBA to a specific LUN.
DM Path States: The device mapper's view of the path condition. Only two conditions are possible:
Active: The last I/O operation sent through this path successfully completed. Analogous to ready path state.
Failed: The last I/O operation sent through this path did not successfully complete. Analogous to faulty path state.
Failover: When a path is determined to be in a failed state, a path that is in a ready state will be made active.[10]
Failback: When a failed path is determined to be active again, multipathd may choose to failback to the path as determined by the failback policy.[11]
Failback Policy: Four options as set in the multipath.conf configuration file.
Immediate: Immediately failback to the highest priority path.
Manual: The failed path is not monitored, requires user intervention to failback.
Followover(for clusters): Only perform automatic failback when the first path of a pathgroup becomes active. This keeps a node from automatically failing back when another node requested the failover.
Number of seconds: Wait for a specified number of seconds to allow the I/O to stabilize, then failback to the highest priority path.
Active/Active: In a system that has two storage controllers, each controller can process I/O.[12]
Active/Passive: In a system that has two storage controllers, only one controller at a time is able to process I/O, the other (passive) is in a standby mode.[12]
