Date: Tue, 29 Apr 2014 11:53:28 +0200 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-scsi@freebsd.org Subject: Re: New iSCSI Stack in 10.x - Prevent hangs on a dead target? Message-ID: <358DDD5C-50F6-4997-9597-3FE40ED9A7B1@FreeBSD.org> In-Reply-To: <C4955EAC8B9007576CC52658@study64.tdx.co.uk> References: <FB27958FDF06CC60D0AC9611@study64.tdx.co.uk> <19D13ADF-EAE2-4CF7-BA67-562444CA0E2A@FreeBSD.org> <C4955EAC8B9007576CC52658@study64.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez Karl Pielorz w dniu 29 kwi 2014, o godz. = 11:14: > --On 29 April 2014 10:43:06 +0200 Edward Tomasz Napiera=B3a = <trasz@FreeBSD.org> wrote: >=20 >> In HEAD, there is "kern.iscsi.fail_on_disconnection" sysctl. It's >> supposed to be used with gmultipath or ZFS; it basically makes = connection >> error result in IO error instead of "hang" until successful = reconnection. >> The initiator will still try to reconnect; when it succeeds, the disk >> devices will reappear. >>=20 >> Would that solve your problem? >=20 > Sounds like it would! - I did have a quick fgrep round the 10-stable = source on the system here - time2retain is mentioned in a .h file - but = I couldn't see any where else it was either used or referenced... >=20 > Do you know if that sysctl/mechanism is likely to be ported to = 10/stable? Yes, in a week or so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?358DDD5C-50F6-4997-9597-3FE40ED9A7B1>