From owner-freebsd-fs@FreeBSD.ORG Mon May 17 18:24:20 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 12A081065724 for ; Mon, 17 May 2010 18:24:20 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id B62228FC17 for ; Mon, 17 May 2010 18:24:14 +0000 (UTC) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta08.westchester.pa.mail.comcast.net with comcast id JcJR1e0081ap0As58iQE7u; Mon, 17 May 2010 18:24:14 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta22.westchester.pa.mail.comcast.net with comcast id JiQC1e00L3S48mS3iiQDZk; Mon, 17 May 2010 18:24:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8DCC59B419; Mon, 17 May 2010 11:24:11 -0700 (PDT) Date: Mon, 17 May 2010 11:24:11 -0700 From: Jeremy Chadwick To: Todd Wasson Message-ID: <20100517182411.GA14251@icarus.home.lan> References: <0B97967D-1057-4414-BBD4-4F1AA2659A5D@duke.edu> <4BF0F231.9000706@mapper.nl> <53F15A8B-77DA-4CEF-A790-2902BEC91002@duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53F15A8B-77DA-4CEF-A790-2902BEC91002@duke.edu> User-Agent: Mutt/1.5.20 (2009-06-14) 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:24:20 -0000 On Mon, May 17, 2010 at 02:17:48PM -0400, Todd Wasson wrote: > 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! Todd, Can you provide some details about the controller you have these disks attached to? "dmesg | egrep -i 'ata|ahci'" should be sufficient at this point. SMART statistics for the drive(s) you feel might be bad would also help. I can try my best to describe the conditions of the disk(s) based on output from "smartctl -a /dev/adX". You can install smartmontools from ports/sysutils/smartmontools. Thanks. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |