From: E.W.Z. <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK annoying messages
Date: Thu, 22 Mar 2018 18:47:03 +0200 [thread overview]
Message-ID: <5ab3de06.84901c0a.693a0.e8f7@mx.google.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AA6BBFDBE@fmsmsx104.amr.corp.intel.com
[-- 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 --]
next reply other threads:[~2018-03-22 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:47 E.W.Z. [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-22 16:55 [SPDK] SPDK annoying messages E.W.Z.
2018-03-22 16:53 E.W.Z.
2018-03-22 16:43 Verkamp, Daniel
2018-03-22 16:34 Andrey Kuzmin
2018-03-22 16:28 Luse, Paul E
2018-03-22 14:49 Ernest Zed
2018-03-22 14:40 Andrey Kuzmin
2018-03-22 11:42 Ernest Zed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ab3de06.84901c0a.693a0.e8f7@mx.google.com \
--to=spdk@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox