Consumer SSD listing namespace as nvme0c0n1 instead of nvme0n1 in /sys/class/ ?

[Nick Neumann]

As part of being careful to not get bit by namespaces whose name
format doesn't match their device
(https://github.com/linux-nvme/nvme-cli/issues/510), I look in
/sys/class/nvme/nvme0 to find the namespaces that belong to /dev/nvme0
.

This has worked well on a ton of consumer NVME devices, and the
namespace has always been of the pattern nvme0n1 . But I recently ran
into a consumer NVME device that listed a namespace of nvme0c0n1 in
/sys/class/nvme/nvme0, and no nvme0n1 .

Running "nvme list" returns the nvme0n1 pattern namespace, and
attempts to use nvme0c0n1 with various tools complain that no such
device exists.Using nvme0n1 as the namespace works.

I've tried reading articles on DM vs native multipathing but it's
still a bit over my head. Is the way this device is presenting itself
incorrect, or is it just an uncommon way of doing things?