Thank you for your reply. I fully forgot about the email thread, but I got the fio working
and able to get my project related to developing a tool for IOPS and latency completed.
The problem was device was removed by the administrator and I got it working. My apologies
for not getting back.
I have few questions about how to handle I/O errors in NVMF initiator, am going to start a
From: SPDK [mailto:email@example.com] On Behalf Of Walker, Benjamin
Sent: Thursday, December 21, 2017 8:51 AM
Subject: Re: [SPDK] Need help for fixing NVMe probe problem in NVMeoF initiator running
On Wed, 2017-12-20 at 21:31 +0000, Sreeni (Sreenivasa) Busam (Stellus) wrote:
./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 --
sync=0 --norandommap --group_reporting --size=12K --runtime=3
nvme: (g=0): rw=rw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T)
4096B-4096B, ioengine=spdk, iodepth=1
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...
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:
Listen RDMA 172.17.2.175:11345
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:
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.