From owner-freebsd-stable@FreeBSD.ORG Thu May 7 13:24:13 2015 Return-Path: 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 DE82B15D for ; Thu, 7 May 2015 13:24:13 +0000 (UTC) Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 761331578 for ; Thu, 7 May 2015 13:24:13 +0000 (UTC) Received: by widdi4 with SMTP id di4so242192701wid.0 for ; Thu, 07 May 2015 06:24:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ju4qAZD1HRMK/5INikufCEUrhlgQfHbsVjU0ZELH+wg=; b=ITVKinpS4p7ycAFVdcoHpoTITY/8HgifyFd1kBdHApQ8Ok8y80MVFz9wIOz2K6uE3X IHmZMPTW4wB+ETgSdF/60yTtUYdT8G1TA2svz6Fsa/O2WHSrwWr+BKOxFwJwk1RG9fWr JYTPg//dMhor+CpRcNj3c6cQZixN1plx8npaXvyz0eVZj3IPviW4qsZut482Y3UR/+Cc +kGzEC5e+kWHKY1v+8A0H4+mkO49H2gipU3+DWLorG5uab/nTDB572zXG8Ix4uuImhbA nZTYqxVlHhzV1t9wwETi008s01nNe9GfJPPXzd8FikjINkA2CWzDwufPVkXzxQHdf8FU qtxA== X-Gm-Message-State: ALoCoQmsjQK1IH9qG30MlazXZc/C8FOBOBg7pJRmgCb+gq87hKxIPSIA5Dgytv3zhk6HFRpQ3dVd X-Received: by 10.194.223.66 with SMTP id qs2mr7777283wjc.6.1431005045176; Thu, 07 May 2015 06:24:05 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id l3sm7431517wiv.18.2015.05.07.06.24.04 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 May 2015 06:24:04 -0700 (PDT) Message-ID: <554B676E.8020500@multiplay.co.uk> Date: Thu, 07 May 2015 14:23:58 +0100 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Slawa Olhovchenkov CC: freebsd-stable@freebsd.org Subject: Re: zfs, cam sticking on failed disk 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> <20150507131007.GZ62239@zxy.spb.ru> In-Reply-To: <20150507131007.GZ62239@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 13:24:14 -0000 On 07/05/2015 14:10, Slawa Olhovchenkov wrote: > 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. In 11 that should be possible with devctl, but under 10 I'm not aware of anything that wouldn't involve some custom kernel level code I'm afraid. Regards Steve