[PATCHv14 00/11] nvme: In-band authentication support
Hannes Reinecke
hare at suse.de
Fri Jun 10 02:12:50 PDT 2022
On 6/10/22 10:55, Chaitanya Kulkarni wrote:
>
>>>
>>> blktests (master) # ./check nvme/039
>>> nvme/039 (Create authenticated connections) [failed]
>>> runtime 1.400s ... 1.707s
>>> --- tests/nvme/039.out 2022-06-08 18:09:06.239931529 -0700
>>> +++ /mnt/data/blktests/results/nodev/nvme/039.out.bad 2022-06-08
>>> 18:09:40.596663692 -0700
>>> @@ -1,6 +1,7 @@
>>> Running nvme/039
>>> +tests/nvme/rc: line 269: printf: write error: Invalid argument
>>> Test unauthenticated connection
>>> -no controller found
>>> +no controller found: failed to write to nvme-fabrics device
>>> NQN:blktests-subsystem-1 disconnected 0 controller(s)
>>> Test authenticated connection
>>> ...
>>> (Run 'diff -u tests/nvme/039.out >
>>> /mnt/data/blktests/results/nodev/nvme/039.out.bad' to see the entire
>> diff)
>>
>> Hmm. Not sure what has happened here, but all blktests worked on my
>> testbed. I'll be rechecking with the latest nvme-cli build.
>>
>> Which nvme-cli version did you use?
>>
>
> ~ # nvme --version
> nvme version 2.0 (git 2.0-96-g0b286b1)
> libnvme version 1.0 (git 1.0-62-gaacaeea)
> ~ #
>
> I'm I using wrong version ?
>
> Can we please add check in the blktests to skip the test
> if we have wrong wrong nvme-cli version ? it will help
> others to not misdiagnosed the problem...
>
Hmm. No, that version looks okay.
What's the kernel message log? Does it say something about 'dev_loss_tmo' ?
If so, can you try with 'export nvme_trtype=tcp' and then running the
tests? Previous versions of nvme-cli had issues with nvme-loop, and were
trying to set the 'dev_loss_tmo' parameter, which isn't valid for loop.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare at suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
More information about the Linux-nvme
mailing list