From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 00:54:57 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CBE116A400 for ; Fri, 13 Jul 2007 00:54:57 +0000 (UTC) (envelope-from stevenschlansker@calmail.berkeley.edu) Received: from smtp-out1.berkeley.edu (smtp-out1.Berkeley.EDU [128.32.61.106]) by mx1.freebsd.org (Postfix) with ESMTP id 899B613C468 for ; Fri, 13 Jul 2007 00:54:57 +0000 (UTC) (envelope-from stevenschlansker@calmail.berkeley.edu) Received: from adsl-75-44-18-150.dsl.pltn13.sbcglobal.net ([75.44.18.150] helo=[192.168.42.3]) by fe2.calmail with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (auth plain:stevenschlansker@berkeley.edu) (envelope-from ) id 1I99CH-0005it-79 for freebsd-current@freebsd.org; Thu, 12 Jul 2007 17:39:49 -0700 Message-ID: <4696C9D2.9070108@calmail.berkeley.edu> Date: Thu, 12 Jul 2007 17:39:46 -0700 From: Steven Schlansker User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4696B0DF.8030909@berkeley.edu> <20070713002611.GA86925@nowhere> In-Reply-To: <20070713002611.GA86925@nowhere> X-Enigmail-Version: 0.94.2.0 OpenPGP: id=40BFF7A7; url=subkeys.pgp.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 13 Jul 2007 02:34:49 +0000 Subject: Re: Removing an accidentally incorrect vdev from a ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2007 00:54:57 -0000 Craig Boston wrote: > On Thu, Jul 12, 2007 at 03:53:19PM -0700, Steven Schlansker wrote: >> I now need to remove this broken vdev from my array. I haven't added >> any data, so there shouldn't even be any data at all on it. However all >> the remove/delete options to zpool seem to exclusively work on mirrors >> and hot spares. I really need to get this vdev off the zfs - it's >> entirely useless. How can I do that? I've already taken out the >> accidental drive - I want to try to recover the old filesystem off of >> it. Lucky it wasn't too important, though it'd be nice to have. Now i >> have an array stuck permanently degraded. > > I don't think it's currently possible to remove a vdev from a pool > without destroying the pool and re-creating it. That being said, it may > be possible to salvage your situation. > > The first thing I would try would be > > zpool replace [pool] ad19 ad18 > > Once the resilver completes, your pool should magically get bigger, > though you may have to export/import the pool first (or reboot if you > can't unmount what's on it). > > If that fails, could you please post the output of 'zpool status' to the > list? > > Craig (Sorry about the duplicate Craig, meant to post that to the list.) Aha! Since I figured it was the wrong hard drive, I opened the case... and voila, my 400GB hard drive was actually installed and showing up incorrectly in dmesg. I replaced the pci interface, and now, a few resilvers and reboots later, everything is peachy. Thanks! Steven