* [SPDK] SPDK annoying messages
@ 2018-03-22 11:42 Ernest Zed
0 siblings, 0 replies; 9+ messages in thread
From: Ernest Zed @ 2018-03-22 11:42 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
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.
Sincerely,
E.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 2700 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:55 E.W.Z.
0 siblings, 0 replies; 9+ messages in thread
From: E.W.Z. @ 2018-03-22 16:55 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 2046 bytes --]
But why I don’t see these namespaces in nvme-cli?
Will check the patch when back to the office
Sent from Mail for Windows 10
From: Verkamp, Daniel
Sent: Thursday, March 22, 2018 6:44 PM
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK annoying messages
Hi Ernest,
Those “inactive NS” messages are skipping namespace IDs that aren’t currently active or in use; your controller probably supports namespace management, and the current NVMe examples just check each reported namespace ID (from 1 to NN as reported in the controller data) to see if they are active.
Newer controllers support a new Identify Active Namespace List command, which provides a way to retrieve this list without iterating over each namespace and calling Identify Namespace. There’s a patch out for review that uses this new feature where available:
https://review.gerrithub.io/#/c/401957/
Thanks,
-- Daniel
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Ernest Zed
Sent: Thursday, March 22, 2018 4:42 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] SPDK annoying messages
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.
Sincerely,
E.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 7189 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:53 E.W.Z.
0 siblings, 0 replies; 9+ messages in thread
From: E.W.Z. @ 2018-03-22 16:53 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 2240 bytes --]
Out of office now, but definitely will check it when will be back.
Sent from Mail for Windows 10
From: Andrey Kuzmin
Sent: Thursday, March 22, 2018 6:34 PM
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK annoying messages
On Thu, Mar 22, 2018, 17:50 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
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(a)gmail.com> wrote:
It looks more like the controller doesn't properly handle the Identify Namespaces command.
Regards,
A.
On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
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.
Sincerely,
E.
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--
Regards,
Andrey
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--
Regards,
Andrey
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 7891 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:47 E.W.Z.
0 siblings, 0 replies; 9+ messages in thread
From: E.W.Z. @ 2018-03-22 16:47 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
Nope, running the perf tool, checking now new 24 NVMe setup
Sent from Mail for Windows 10
From: Luse, Paul E
Sent: Thursday, March 22, 2018 6:28 PM
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK annoying messages
Are you running the hello_wrold example below? Have you tried running /examples/identify just to see what kind of info you get back?
-Paul
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Ernest Zed
Sent: Thursday, March 22, 2018 7:50 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] SPDK annoying messages
So I guess, nothing could be done to solve it, right?
On Thu, Mar 22, 2018 at 4:40 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com> wrote:
It looks more like the controller doesn't properly handle the Identify Namespaces command.
Regards,
A.
On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
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.
Sincerely,
E.
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
--
Regards,
Andrey
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 9638 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:43 Verkamp, Daniel
0 siblings, 0 replies; 9+ messages in thread
From: Verkamp, Daniel @ 2018-03-22 16:43 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
Hi Ernest,
Those “inactive NS” messages are skipping namespace IDs that aren’t currently active or in use; your controller probably supports namespace management, and the current NVMe examples just check each reported namespace ID (from 1 to NN as reported in the controller data) to see if they are active.
Newer controllers support a new Identify Active Namespace List command, which provides a way to retrieve this list without iterating over each namespace and calling Identify Namespace. There’s a patch out for review that uses this new feature where available:
https://review.gerrithub.io/#/c/401957/
Thanks,
-- Daniel
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Ernest Zed
Sent: Thursday, March 22, 2018 4:42 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: [SPDK] SPDK annoying messages
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.
Sincerely,
E.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 6642 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:34 Andrey Kuzmin
0 siblings, 0 replies; 9+ messages in thread
From: Andrey Kuzmin @ 2018-03-22 16:34 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
On Thu, Mar 22, 2018, 17:50 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
> 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(a)gmail.com>
> wrote:
>
>> It looks more like the controller doesn't properly handle the Identify
>> Namespaces command.
>>
>> Regards,
>> A.
>>
>> On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
>>
>>> 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.
>>>
>>> Sincerely,
>>> E.
>>> _______________________________________________
>>> SPDK mailing list
>>> SPDK(a)lists.01.org
>>> https://lists.01.org/mailman/listinfo/spdk
>>>
>> --
>>
>> Regards,
>> Andrey
>>
>> _______________________________________________
>> SPDK mailing list
>> SPDK(a)lists.01.org
>> https://lists.01.org/mailman/listinfo/spdk
>>
>>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
--
Regards,
Andrey
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5783 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 16:28 Luse, Paul E
0 siblings, 0 replies; 9+ messages in thread
From: Luse, Paul E @ 2018-03-22 16:28 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
Are you running the hello_wrold example below? Have you tried running /examples/identify just to see what kind of info you get back?
-Paul
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Ernest Zed
Sent: Thursday, March 22, 2018 7:50 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] SPDK annoying messages
So I guess, nothing could be done to solve it, right?
On Thu, Mar 22, 2018 at 4:40 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com<mailto:andrey.v.kuzmin(a)gmail.com>> wrote:
It looks more like the controller doesn't properly handle the Identify Namespaces command.
Regards,
A.
On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com<mailto:kreuzerkrieg(a)gmail.com>> wrote:
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.
Sincerely,
E.
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk
--
Regards,
Andrey
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org<mailto:SPDK(a)lists.01.org>
https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 7262 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 14:49 Ernest Zed
0 siblings, 0 replies; 9+ messages in thread
From: Ernest Zed @ 2018-03-22 14:49 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
So I guess, nothing could be done to solve it, right?
On Thu, Mar 22, 2018 at 4:40 PM, Andrey Kuzmin <andrey.v.kuzmin(a)gmail.com>
wrote:
> It looks more like the controller doesn't properly handle the Identify
> Namespaces command.
>
> Regards,
> A.
>
> On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
>
>> 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.
>>
>> Sincerely,
>> E.
>> _______________________________________________
>> SPDK mailing list
>> SPDK(a)lists.01.org
>> https://lists.01.org/mailman/listinfo/spdk
>>
> --
>
> Regards,
> Andrey
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
>
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4521 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [SPDK] SPDK annoying messages
@ 2018-03-22 14:40 Andrey Kuzmin
0 siblings, 0 replies; 9+ messages in thread
From: Andrey Kuzmin @ 2018-03-22 14:40 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
It looks more like the controller doesn't properly handle the Identify
Namespaces command.
Regards,
A.
On Thu, Mar 22, 2018, 14:42 Ernest Zed <kreuzerkrieg(a)gmail.com> wrote:
> 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.
>
> Sincerely,
> E.
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
>
--
Regards,
Andrey
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3551 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-03-22 16:55 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-22 11:42 [SPDK] SPDK annoying messages Ernest Zed
2018-03-22 14:40 Andrey Kuzmin
2018-03-22 14:49 Ernest Zed
2018-03-22 16:28 Luse, Paul E
2018-03-22 16:34 Andrey Kuzmin
2018-03-22 16:43 Verkamp, Daniel
2018-03-22 16:47 E.W.Z.
2018-03-22 16:53 E.W.Z.
2018-03-22 16:55 E.W.Z.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.