Re: kernull NULL pointer observed on initiator side after 'nvmetcli clear' on target side

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/17/2017 12:40 AM, Sagi Grimberg wrote:

The target was deleted by 'nvmetcli clear' command.
Then on client side, seems it doesn't know the target side was deleted
and will always reconnecting in 10 seconds.

Oh, so the target doesn't come back. That makes sense. The host
doesn't know if/when the target will come back so it attempts reconnect
periodically forever.

I think what you're asking is a "dev_loss_tmo" kind of functionality
where the host gives up on the controller correct?
Hi Sagi
Yes, since the target was deleted, but the client doesn't realized it and always reconnect it.
I think it's better to stop the reconnect operation. Or any other good idea?
Since I'm a newbie and not familiar with for nvme-of, correct if my thought not reasonable. :)

Thanks
Yi

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux