All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Need help for fixing NVMe probe problem in NVMeoF initiator running fio.
Date: Thu, 21 Dec 2017 16:50:45 +0000	[thread overview]
Message-ID: <1513875044.2658.19.camel@intel.com> (raw)
In-Reply-To: 21fe5140fda84728ab84ea5bd3027020@stellus.com

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]

On Wed, 2017-12-20 at 21:31 +0000, Sreeni (Sreenivasa) Busam (Stellus) wrote:
>   Initiator log:
>     ./fio --name=nvme --numjobs=1 --filename="trtype=RDMA adrfam=IPV4
> traddr=172.17.2.175 trsvcid=11345 subnqn=nqn.2017-06.io.spdk-MPcnode1 ns=1" --
> bs=4K --iodepth=1 --
> ioengine=/home.local/sfast/spdk20/spdk/examples/nvme/fio_plugin/fio_plugin --
> sync=0 --norandommap --group_reporting --size=12K --runtime=3 -rwmixwrite=30
> --thread=1 --rw=rw
>     nvme: (g=0): rw=rw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B,
> ioengine=spdk, iodepth=1
>     fio-3.3
>     Starting 1 thread
>     Starting DPDK 17.11.0 initialization...
>     [ DPDK EAL parameters: fio -c 0x1 -m 512 --file-prefix=spdk_pid28214 ]
>     EAL: Detected 32 lcore(s)
>     EAL: No free hugepages reported in hugepages-1048576kB
>     EAL: Probing VFIO support...
>     nvme_ctrlr.c:1031:nvme_ctrlr_construct_namespaces: *ERROR*: controller has
> 0 namespaces
>     fio_plugin.c: 298:spdk_fio_setup: *ERROR*: spdk_nvme_probe()

This error means your NVMe-oF subsystem does not have any namespaces. That
usually means there is a problem in the configuration file.

>     NVMF configuration file:
>     [Nvmf]
>       MaxQueuesPerSession 4
>       AcceptorPollRate 10000
>  
>     [Subsystem1]
>       NQN nqn.2017-06.io.spdk-MPcnode1
>       Core 1
>       SN  SPDK0000000000000001
>       Listen RDMA 172.17.2.175:11345
>       AllowAnyHost Yes
>       NVMe 0000:84:00.0

What version of SPDK are you using? The NVMe directive inside of the [Subsystem]
section was replaced with syntax that looks like this:

Namespace Nvme0n1 1

And Nvme0n1 is defined by the [Nvme] section with syntax like this:

[Nvme]
TransportId "trtype:PCIe traddr:0000:00:00.0" Nvme0

See etc/spdk/nvmf.conf.in for a full example. If you upgraded SPDK to a newer
version but didn't update your configuration file, you'll end up with a
subsystem with 0 namespaces because it doesn't understand the NVMe directive
anymore.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]

             reply	other threads:[~2017-12-21 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 16:50 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-22 17:52 [SPDK] Need help for fixing NVMe probe problem in NVMeoF initiator running fio Sreeni Busam
2017-12-20 21:31 Sreeni Busam

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=1513875044.2658.19.camel@intel.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 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.