[stgt] Why tgtd keeps connecting for one hour ?
ronniesahlberg at gmail.com
Tue May 28 00:50:59 CEST 2013
What you see is probably that it takes one hour for the TCP Keepalives
to detect that the other end of the tcp connection is dead.
A better, and quicker, way for a target to detect that an initiator
is no longer reachable is using NOP-OUT pings.
I just sent a patch to the list to add this for iscsi.
You could try building TGTD with that patch and see if it solves your problem.
In order to activate it you need to specify '--iscsi
noop_interval=5,noop_count=6' on the command line when you start TGTD.
noop_interval and noop_count controls how frequently TGTD will send a
NOP-OUT to the initiator and after how many failures
it will tear down the connection.
You probably shouldnt set this too low, to allow the session to
survuve across a short network glitch, but something like 5,6 like
above could be a good setting.
It would allow you to detect and tear down the connection after ~30 seconds
On Tue, May 14, 2013 at 9:37 PM, YOUN-SANG KIM <mistkr at gmail.com> wrote:
> tgtadm --lld iscsi --op show --mode conn --tid 1
> shows that tgtd keeps connecting for one hour, nevertheless initiator
> (iPXE iscsi boot WIndows PC) is turned off normally
> When I restarted Windows with iPXE iscsi boot, one connection are
> increased per each restart.
> Nevertheless initiator (iPXE iscsi boot WIndows PC) is turned off normally
> why tgtd keeps connecting for one hour ?
> Can I reduce this keep-connection time ?
> or can I disconnect all connection of specific target ?
> To unsubscribe from this list: send the line "unsubscribe stgt" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the stgt