Out of office now, but definitely will check it when will be back.
Sent from Mail for Windows 10
So I guess, nothing could be done to solve it, right?
You might want to see what Identify Namespaces actually gives you, and why it's not getting properly terminated following the only real namespace. Adding a quirk to the spdk identify implementation would then resolve your issue.
Regards,
A.
On Thu, Mar 22, 2018 at 4:40 PM, Andrey Kuzmin <andrey.v.kuzmin@gmail.com> wrote:
It looks more like the controller doesn't properly handle the Identify Namespaces command.
A.
Hi,
I'm using Ultrastar SN200 Series PCIe SSD, the `nvme list` shows that each disk has 1 namespace, but when attaching to controller SPDK sprinkles all over with following messages:
EAL: PCI device 0000:9f:00.0 on NUMA socket 1
EAL: probe driver: 1c58:23 spdk_nvme
Attaching to NVMe Controller at 0000:9f:00.0 [1c58:0023]
Attached to NVMe Controller at 0000:9f:00.0 [1c58:0023]
Controller HUSMR7680BDP301 (SDM00001A6F7 ): Skipping inactive NS 2
Controller HUSMR7680BDP301 (SDM00001A6F7 ): Skipping inactive NS 3
Controller HUSMR7680BDP301 (SDM00001A6F7 ): Skipping inactive NS ...
Controller HUSMR7680BDP301 (SDM00001A6F7 ): Skipping inactive NS 128
What is it? is it some SPDK bug? since when I try to erase those using `nvme delete-ns` it says there is no such a namespace.
_______________________________________________
SPDK mailing list
SPDK@lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--
_______________________________________________
SPDK mailing list
SPDK@lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK@lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--
Regards,
Andrey