[SPDK] Re: Query about "Starting I/O failed" exception while using arbitration NVMe example

Walker, Benjamin <benjamin.walker at intel.com>
Newsgroups dev.linux.lists.spdk
Message-ID <BYAPR11MB282433A8FA62A2D28034E377EF9B0@BYAPR11MB2824.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Harshit Jain <kumarjain10(a)gmail.com>
> Sent: Tuesday, June 16, 2020 10:26 PM
> To: spdk(a)lists.01.org
> Subject: [SPDK] Query about "Starting I/O failed" exception while using
> arbitration NVMe example
> 
> Hello Team,
> 
> I was trying to setup SPDK on Linux Kernel 5.6.4 and get started on using SPDK
> examples. I hope I have posted the query in the right forum thread.
> 
> I was trying to setup SPDK on Linux Kernel 5.6.4. While trying to execute the
> NVMe arbitration example, I am facing Starting I/O failed exception. I have
> added debug prints to get the value of error and it was -22.
> 
> The attached NVMe SSD has a single namespace of 64MB and 4k sector size
> format and single controller. Since basic script was giving exception, I tried
> reducing the IO count to 1 and io size in bytes to 4096 to keep the IO profile
> simple. But I still faced the same exception.
> 
> Is there any configuration missing while setting up SPDK?
> 
> I have tried most of the other examples too, it is observed that NVMe Admin
> commands and queue creation is working fine but the example script is unable
> to submit NVM I/O commands to the controller due to the mentioned
> exception.
> 
> SPDK version
> Starting SPDK v20.07-pre git sha1 e69375b / DPDK 19.11.0 initialization...

Can you confirm if the other tools like identify and perf are working for you? Does the identify tool report that you device supports arbitration?


> 
> 
> Thanks in advance.
> 
> Regards,
> Harshit
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.