multipath-nvme · shipping

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

  1. Linux kernel documentation: Linux NVMe multipath, introduction and policies. (accessed 2026-10-11)
  2. Storage fencing: why a lost heartbeat does not stop writes (accessed 2026-10-11)
  3. Linux v6.12, drivers/nvme/host/multipath.c: ANA selection, controller nr_active accounting and subsystem iopolicy. (accessed 2026-10-15)
  4. Linux v6.12 NVMe host core: shared namespace identity checks and device naming. (accessed 2026-10-16)

Further reading

  1. NVMe multipath (accessed 2026-03-26)
  2. Hesela: NVMe multipath: ANA access states and Linux path policies (accessed 2026-10-15)

JSON: /data/terms/multipath-nvme.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. NVMe multipath. Hesela. 2026-10-16. https://hesela.dev/terms/multipath-nvme/