Host reconnecting need more than 60s to start after nvmetcli clear on target

Yi Zhang yizhan at redhat.com
Tue Sep 19 02:09:05 PDT 2017



On 09/18/2017 11:58 PM, Christoph Hellwig wrote:
> On Fri, Sep 08, 2017 at 07:44:37AM -0400, Yi Zhang wrote:
>> Hi
>>
>> I found this issue on latest 4.13, is it for designed?  I cannot reproduce it on 4.12.
>>
>> Here is the log from host:
>> 4.13
>> [  637.246798] nvme nvme0: new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery", addr 172.31.0.90:4420
>> [  637.436315] nvme nvme0: creating 40 I/O queues.
>> [  637.939988] nvme nvme0: new ctrl: NQN "testnqn", addr 172.31.0.90:4420
>> [  645.319803] nvme nvme0: rescanning
>>
>> -->need more than 60 seconds to start reconnect
>>
>> [  706.073551] nvme nvme0: Reconnecting in 10 seconds...
> How did you initiate the reconnect?  Cable drop?

Just execute "nvmetcli clear" on target side, and check the log on host 
side.

> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme




More information about the Linux-nvme mailing list