Date: Tue, 29 Apr 2014 10:14:41 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@FreeBSD.org> Cc: freebsd-scsi@freebsd.org Subject: Re: New iSCSI Stack in 10.x - Prevent hangs on a dead target? Message-ID: <C4955EAC8B9007576CC52658@study64.tdx.co.uk> In-Reply-To: <19D13ADF-EAE2-4CF7-BA67-562444CA0E2A@FreeBSD.org> References: <FB27958FDF06CC60D0AC9611@study64.tdx.co.uk> <19D13ADF-EAE2-4CF7-BA67-562444CA0E2A@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
--On 29 April 2014 10:43:06 +0200 Edward Tomasz Napierała <trasz@FreeBSD.org> wrote: > 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. > > Would that solve your problem? 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... Do you know if that sysctl/mechanism is likely to be ported to 10/stable? Thanks, -Karlhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C4955EAC8B9007576CC52658>