From owner-freebsd-fs@FreeBSD.ORG Sun May 16 21:24:00 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDEA0106566B for ; Sun, 16 May 2010 21:24:00 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5FDF28FC1C for ; Sun, 16 May 2010 21:24:00 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-243-123.shv.bellsouth.net [98.67.243.123]) (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 823C686D9B26; Sun, 16 May 2010 16:23:59 -0500 (CDT) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.4/8.14.4) with ESMTP id o4GLNugx023337; Sun, 16 May 2010 16:23:56 -0500 (CDT) (envelope-from morganw@chemikals.org) Date: Sun, 16 May 2010 16:23:56 -0500 (CDT) From: Wes Morgan X-X-Sender: morganw@volatile To: Todd Wasson In-Reply-To: <0BE564E4-3B13-41A5-9A38-7D5AE0C983BF@duke.edu> Message-ID: References: <0B97967D-1057-4414-BBD4-4F1AA2659A5D@duke.edu> <6FADBEDC-FF47-498A-BB17-0FCC163D3C8C@duke.edu> <0BE564E4-3B13-41A5-9A38-7D5AE0C983BF@duke.edu> 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 drive replacement issues 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: Sun, 16 May 2010 21:24:00 -0000 On Sun, 16 May 2010, Todd Wasson wrote: > >>> Strange, you should be able to cancel the replacement with detach. There > >>> is some kind of DTL issue preventing it. I don't know what it is > >>> precisely, but there are known cases where legitimate detach operations > >>> are prevented. > >>> > >>> Try reconnecting the disk you partitioned, leaving the original ad6 still > >>> attached, and you should be able to detach the new one. > >> > >> The problem with that is that I can't have any more than four SATA > >> devices in my machine. I'd have to detach one of the other (good) > >> devices in order to do that. Is that feasible / possible? I would > >> think at that point I would have only two of the four drives in the pool > >> and it wouldn't function at all, but if that's not the case I can give > >> it a try... > > > > I wouldn't recommend that. What about attaching it externally, via eSATA > > or USB? > > Unfortunately, my machine doesn't support eSATA and I don't have a USB > to SATA adapter. I can pick one up if it'll help me solve this, though, > but one related issue: will the device be identified as the device that > used to be on ad6 (or ad6s1) once it's attached via another means, like > a USB adapter? I suspect it will (or that I can issue a command to tell > the zpool about it, anyway) but I thought I'd double check... Via USB, it will show up as a daX device, and it should be recognized without problem by zfs. You may need to export and import the pool, though.