From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 00:26:18 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 0B2B216A400 for ; Fri, 13 Jul 2007 00:26:18 +0000 (UTC) (envelope-from craig@xfoil.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id EB8F413C448 for ; Fri, 13 Jul 2007 00:26:15 +0000 (UTC) (envelope-from craig@xfoil.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 9772E111F3; Thu, 12 Jul 2007 19:26:15 -0500 (CDT) Date: Thu, 12 Jul 2007 19:26:11 -0500 From: Craig Boston To: Steven Schlansker Message-ID: <20070713002611.GA86925@nowhere> Mail-Followup-To: Craig Boston , Steven Schlansker , freebsd-current@freebsd.org References: <4696B0DF.8030909@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4696B0DF.8030909@berkeley.edu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org 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:26:18 -0000 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