NVMe multipath
Using multiple routes to the same NVMe namespace for path failover and, where supported, load distribution.
Linux native NVMe multipath presents paths to the same namespace within an NVM subsystem as one block device. ANA access preference precedes the host's selection policy. [2] More routes are not more replicas, and their physical failure independence must be checked separately. If no usable path exists, I/O can wait or fail; this is not a guarantee of interruption-free failover. [4] Path routing also does not grant exclusive write ownership. [3] Linux v6.12 checks shared-path identifier consistency within the subsystem, while device names use allocated instances rather than protocol NSIDs. [6]
Relations
- related
- NVMe, Multipath I/O, Enterprise SSD, ALUA, Asymmetric Namespace Access, I/O fencing, NVMe multipath I/O policy, NVMe namespace, NVMe base specification, NVMe namespace ID (NSID), NVMe namespace identifiers, NVMe subsystem NQN, SCSI persistent reservations
Citations
- Linux kernel documentation: Linux NVMe multipath, introduction and policies.
- Storage fencing: why a lost heartbeat does not stop writes
- Linux v6.12, drivers/nvme/host/multipath.c: ANA selection, controller nr_active accounting and subsystem iopolicy.
- Linux v6.12 NVMe host core: shared namespace identity checks and device naming.