From owner-freebsd-fs@FreeBSD.ORG Fri Apr 30 01:06:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87746106566B for ; Fri, 30 Apr 2010 01:06:31 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (warped.bluecherry.net [66.138.159.247]) by mx1.freebsd.org (Postfix) with ESMTP id 5CAD48FC0A for ; Fri, 30 Apr 2010 01:06:31 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-123-77.shv.bellsouth.net [98.67.123.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 0688D87DC615; Thu, 29 Apr 2010 20:06:29 -0500 (CDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.4/8.14.4) with ESMTP id o3U16P39071566; Thu, 29 Apr 2010 20:06:25 -0500 (CDT) (envelope-from morganw@chemikals.org) Date: Thu, 29 Apr 2010 20:06:25 -0500 (CDT) From: Wes Morgan X-X-Sender: morganw@volatile To: Freddie Cash In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.95.3 at warped X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: "Cannot replace a replacing drive" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2010 01:06:31 -0000 On Wed, 28 Apr 2010, Freddie Cash wrote: > Going through the archives, I see that others have run into this issue, and > managed to solve it via "zpool detach". However, looking closely at the > archived messages, all the successful tests had one thing in common: 1 > drive ONLINE, 1 drive FAULTED. If a drive is online, obviously it can be > detached. In all the cases where people have been unsuccessful at fixing > this situation, 1 drive is OFFLINE, and 1 drive is FAULTED. As is our case: > What happened to the drive to fault it?