From owner-freebsd-fs@FreeBSD.ORG Mon May 17 18:17:50 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 1F37B1065673 for ; Mon, 17 May 2010 18:17:50 +0000 (UTC) (envelope-from tsw5@duke.edu) Received: from smtp.duke.edu (smtp-01.oit.duke.edu [152.3.174.14]) by mx1.freebsd.org (Postfix) with ESMTP id EAE838FC08 for ; Mon, 17 May 2010 18:17:49 +0000 (UTC) Received: from smtp.duke.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 339A3308F5D; Mon, 17 May 2010 14:17:49 -0400 (EDT) Received: from user-152-3-155-113.wireless.duke.edu (user-152-3-155-113.wireless.duke.edu [152.3.155.113]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.duke.edu (Postfix) with ESMTP id 17A34308DE4; Mon, 17 May 2010 14:17:49 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Todd Wasson In-Reply-To: <4BF0F231.9000706@mapper.nl> Date: Mon, 17 May 2010 14:17:48 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <53F15A8B-77DA-4CEF-A790-2902BEC91002@duke.edu> References: <0B97967D-1057-4414-BBD4-4F1AA2659A5D@duke.edu> <4BF0F231.9000706@mapper.nl> To: Mark Stapper X-Mailer: Apple Mail (2.1078) X-PMX-Version: 5.4.2.338381, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2010.5.17.180314 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: Mon, 17 May 2010 18:17:50 -0000 > Hello, > You could try exporting and importing the pool with three disks. > Then make sure the "new" drive isn't part of any zpool (low-level = format?). > Then try a "replace" again. > Have fun! >=20 Hi Mark, I was about to try this, but I just tried putting the "old" = (damaged) drive back in the pool and detaching the "new" drive from the = pool, which I've tried before, but for some reason this time it = succeeded. I was then able to "zpool offline" the old drive, physically = replace it with the new one, and "zpool replace" the old one with the = new one. It just finished successfully resilvering, and apparently = everything is working well. I'm going to initiate a scrub to be sure = that everything is alright, but I'm fairly sure that the problem is = solved. I didn't do anything that I hadn't already tried, so I don't = know why it worked this time, but I'm not complaining. Thanks to = everyone for your help; at the very least, the idea of putting the = original drive back into the machine and mucking around with it led me = in the right direction. Next time I'll be sure to issue an offline = command before replacing a device! Thanks again. Todd=