Date: Thu, 7 May 2015 13:46:55 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: zfs, cam sticking on failed disk Message-ID: <20150507104655.GT62239@zxy.spb.ru> In-Reply-To: <554B40B6.6060902@multiplay.co.uk> References: <20150507080749.GB1394@zxy.spb.ru> <554B2547.1090307@multiplay.co.uk> <20150507095048.GC1394@zxy.spb.ru> <554B40B6.6060902@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 07, 2015 at 11:38:46AM +0100, Steven Hartland wrote: > >>> How I can cancel this 24 requst? > >>> Why this requests don't timeout (3 hours already)? > >>> How I can forced detach this disk? (I am lready try `camcontrol reset`, `camconrol rescan`). > >>> Why ZFS (or geom) don't timeout on request and don't rerouted to da18? > >>> > >> If they are in mirrors, in theory you can just pull the disk, isci will > >> report to cam and cam will report to ZFS which should all recover. > > Yes, zmirror with da18. > > I am surprise that ZFS don't use da18. All zpool fully stuck. > A single low level request can only be handled by one device, if that > device returns an error then ZFS will use the other device, but not until. Why next requests don't routed to da18? Current request stuck on da19 (unlikely, but understund), but why stuck all pool?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150507104655.GT62239>