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:53:41 +0200 [thread overview]
Message-ID: <5ab3df94.480f1c0a.77363.9451@mx.google.com> (raw)
In-Reply-To: CANvN+em6ze8XCU1OSTOCKQGf+sreTsVhzopESb0rTZrC0WboNA@mail.gmail.com
[-- 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 --]
next reply other threads:[~2018-03-22 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:53 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:47 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=5ab3df94.480f1c0a.77363.9451@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