From owner-freebsd-stable@FreeBSD.ORG  Thu May  7 13:10:11 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 279FFE6F
 for <freebsd-stable@freebsd.org>; Thu,  7 May 2015 13:10:11 +0000 (UTC)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D21141333
 for <freebsd-stable@freebsd.org>; Thu,  7 May 2015 13:10:10 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1YqLZ1-00036e-Vz; Thu, 07 May 2015 16:10:08 +0300
Date: Thu, 7 May 2015 16:10:07 +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: <20150507131007.GZ62239@zxy.spb.ru>
References: <20150507095048.GC1394@zxy.spb.ru>
 <554B40B6.6060902@multiplay.co.uk>
 <20150507104655.GT62239@zxy.spb.ru>
 <554B53E8.4000508@multiplay.co.uk>
 <20150507120508.GX62239@zxy.spb.ru>
 <554B5BF9.8020709@multiplay.co.uk>
 <20150507124416.GD1394@zxy.spb.ru>
 <554B5EB0.1080208@multiplay.co.uk>
 <20150507125129.GY62239@zxy.spb.ru>
 <554B6307.9020309@multiplay.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <554B6307.9020309@multiplay.co.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2015 13:10:11 -0000

On Thu, May 07, 2015 at 02:05:11PM +0100, Steven Hartland wrote:

> 
> 
> On 07/05/2015 13:51, Slawa Olhovchenkov wrote:
> > On Thu, May 07, 2015 at 01:46:40PM +0100, Steven Hartland wrote:
> >
> >>>> Yes in theory new requests should go to the other vdev, but there could
> >>>> be some dependency issues preventing that such as a syncing TXG.
> >>> Currenly this pool must not have write activity (from application).
> >>> What about go to the other (mirror) device in the same vdev?
> >>> Same dependency?
> >> Yes, if there's an outstanding TXG, then I believe all IO will stall.
> > Where this TXG released? When all devices in all vdevs report
> > 'completed'? When at the least one device in all vdevs report
> > 'completed'? When at the least one device in at least one vdev report
> > 'completed'?
> When all devices have report completed or failed.

Thanks for explained.

> Hence if you pull the disk things should continue as normal, with the 
> failed device being marked as such.

I am have trouble to phisical access.
May be someone can be suggest software method to forced detach device
from system.