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.