From owner-freebsd-fs@FreeBSD.ORG  Sat Jun 20 05:43:31 2009
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 939BF106564A
	for <freebsd-fs@freebsd.org>; Sat, 20 Jun 2009 05:43:31 +0000 (UTC)
	(envelope-from mat.macy@gmail.com)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240])
	by mx1.freebsd.org (Postfix) with ESMTP id 477B18FC12
	for <freebsd-fs@freebsd.org>; Sat, 20 Jun 2009 05:43:31 +0000 (UTC)
	(envelope-from mat.macy@gmail.com)
Received: by an-out-0708.google.com with SMTP id c3so964616ana.13
	for <freebsd-fs@freebsd.org>; Fri, 19 Jun 2009 22:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:sender:received:in-reply-to
	:references:date:x-google-sender-auth:message-id:subject:from:to:cc
	:content-type:content-transfer-encoding;
	bh=pMvKDyYT1T39ibpcUaf6szBmV/Dzoa6Z/f2cP2zjDfY=;
	b=ezR/e9ahB6JwmAliuVSvXiUyBYyc6V8kOgG3gVoi94uogzyuarRd0GQG+3BBrmedH2
	Wj0JlniYhd9gxq4OatoDAjxxPtWKqKwDDFflmnvE8sToAeTg82agfk2LXmrtzqBUFu7k
	8cC1PzNkfslnLczRH4LXjgJYD367NjH67E39M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	b=tvcd7aKHCnYwG83ezFsNXDR+BZXAbOdmUk9SJuRzJoUhI9qIT9Afc2m3jFdBPrtjd5
	mZuBfRwwdj0rEIZQR3p3Dhq22KS4hdTB2pUFTiHDg2lzPmESoQkArO0LNcNXbvj65yT+
	ZaJHfRGEj1UXDkNf214TX3WnZ+yMapRg6JjgE=
MIME-Version: 1.0
Sender: mat.macy@gmail.com
Received: by 10.100.46.3 with SMTP id t3mr4888679ant.94.1245476610334; Fri, 19 
	Jun 2009 22:43:30 -0700 (PDT)
In-Reply-To: <20090620045357.GB22846@server.vk2pj.dyndns.org>
References: <m2bpol6v8r.wl%randy@psg.com> <4A3B1020.2010305@jrv.org>
	<20090620045357.GB22846@server.vk2pj.dyndns.org>
Date: Fri, 19 Jun 2009 22:43:30 -0700
X-Google-Sender-Auth: 97c438b1e3d0ec55
Message-ID: <3c1674c90906192243g2ea0781ne66fb67a520d56bf@mail.gmail.com>
From: Kip Macy <kmacy@freebsd.org>
To: Peter Jeremy <peterjeremy@optushome.com.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-fs <freebsd-fs@freebsd.org>, Randy Bush <randy@psg.com>
Subject: Re: adding drive to raidz1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2009 05:43:31 -0000

> Both these are unfortunate restrictions. =A0I can understand that
> expanding a RAIDZ would be a fairly complex operation but it's
> probably the most requested feature. =A0I'm surprised that Sun don't
> allow removing vdevs from a pool - it's orthogonal to adding a vdev to
> a pool and (eg) HP AdvFS allows both.


http://blogs.sun.com/ahl/entry/expand_o_matic_raid_z

This has a very good discussion of how it could be done along with why
it hasn't been done.

Cheers,
Kip