Differences

This shows you the differences between two versions of the page.

--- nndocs:nvme-of [2024/02/24 21:34] – [Target] clarify a little, I hope naptastic
+++ nndocs:nvme-of [2025/10/26 23:45] (current) – snark +1 naptastic
@@ Line 1: / Line 1: @@
-TODO Please put storage traffic on its own IB subnet and limit things sanely.
-NQNs: nqn.2014-08.rocks.narf.hostname is the whole thing. No :01 or any of that jazz, at least not yet.
 The goal is to run everything over RDMA (InfiniBand specifically) and maybe have TCP as a fallback. (If TCP, then I probably want to try VMA... which I don't want to do.)
@@ Line 10: / Line 6: @@
 Create the subsystem:
     /> subsystems/ create nqn.2014-08.rocks.narf.southpark
+NVMe calls network ports "service IDs", and has their own idea for "ports". Good for them.
 Create a port and set its properties:
@@ Line 19: / Line 17: @@
     /> ports/1/subsystems create nqn.2014-08.rocks.narf.southpark
-NVMe uses "namespaces" (which are numbers) instead of LUNs. Good for them.
+NVMe calls LUNs "namespaces" (which are numbers). Good for them.
 Create, set, and enable namespace:
     /> subsystems/nqn.2014-08.rocks.narf.southpark/namespaces create 1
-    /> subsystems/nqn.2014-08.rocks.narf.southpark/namespaces/1 set device path=/dev/nvme0n1
+    /> subsystems/nqn.2014-08.rocks.narf.southpark/namespaces/1 set device path=/dev/disk/by-id/nvme-eui.foo
     /> subsystems/nqn.2014-08.rocks.narf.southpark/namespaces/1 enable
+Don't use /dev/nvme* names; they can change order on reboot.
 You can use a file as a backstore. The syntax is not at all obvious. Why "group=device"? Whatever:
@@ Line 50: / Line 50: @@
 Log in:
     # nvme connect -t rdma -n nqn.2014-08.rocks.narf.southpark -a 172.20.64.13 -s 4420
+Rescan:
+    # nvme ns-rescan /dev/nvme1
+  * If a namespace you expect to appear isn't appearing, check the target to see if you forget to enable it
 Disconnect a subsystem: