NVMe device names follow this pattern: nvme <number> n <namespace> , where: <number> is an integer that is assigned by Linux during the boot process. The first NVMe device that is detected is assigned 0
I still don’t understand the point of namespaces. I guess it’s less overhead to pass through a namespace to a VM rather than having a virtualised disk image or bind mount.
nvme0n1p1
mmcblkxpy
(SD Card)
x = device number
y = partition number
NVMe device names follow this pattern: nvme <number> n <namespace> , where: <number> is an integer that is assigned by Linux during the boot process. The first NVMe device that is detected is assigned 0
You also can have a ‘c’ in there, when it wants to model multipath nvme…
I still don’t understand the point of namespaces. I guess it’s less overhead to pass through a namespace to a VM rather than having a virtualised disk image or bind mount.
The other dragons aren’t specifying a partition
So the 3rd dragon should just be
/dev/nvme%dONIPI
This made me chuckle, thank you!!