hesela.devNVMe discovery controller
An NVMe discovery controller supplies information for locating NVM subsystems or other discovery services without exposing namespaces or implementing I/O queues.
Scope: Discovery records describe connection endpoints and can refer to another discovery service. Discovery controllers do not execute namespace I/O [1].
Identity: The well-known discovery NQN is not the only possible name; the architecture also supports unique Discovery Service NQNs [1].
Operations: Discovery retrieves connection information. Path selection belongs to multipath logic, including ANA-state handling, so a discovery result alone does not demonstrate working failover [2] [3].
Relations
- related
- nvme-of, nvme-tcp, nvme-rdma, nvm-subsystem, nvme-subsystem-nqn, multipath-nvme
Citations
- NVM Express Base Specification 2.2, section 3.1.3.3: Discovery Controllers
- nvme-cli v2.11: nvme-discover
- Linux native NVMe multipath: ANA states and path-selection policies
Sources & caveats
- Controller scope and naming are pinned to Base 2.2. The failover distinction is an architectural inference from the separate discovery and path-selection roles.