From owner-freebsd-fs@freebsd.org  Mon May 21 08:57:48 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 402DAEE8DE4
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 21 May 2018 08:57:48 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com
 [195.16.148.151])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C57F974B1C
 for <freebsd-fs@freebsd.org>; Mon, 21 May 2018 08:57:47 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.141] (unknown [192.148.167.11])
 by proxypop02.sare.net (Postfix) with ESMTPA id 10BAB9DC847;
 Mon, 21 May 2018 10:52:15 +0200 (CEST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Question about zpool remove vdev
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <130DDCA4-55C6-40DC-A53D-D2E031DCA9B2@sarenet.es>
Date: Mon, 21 May 2018 10:52:13 +0200
Cc: freebsd-fs@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <10FC394B-C557-439A-9D0E-BB5CEDD00195@sarenet.es>
References: <130DDCA4-55C6-40DC-A53D-D2E031DCA9B2@sarenet.es>
To: Borja Marcos <borjam@sarenet.es>
X-Mailer: Apple Mail (2.3445.6.18)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 May 2018 08:57:48 -0000



> On 21 May 2018, at 10:37, Borja Marcos <borjam@sarenet.es> wrote:
>=20
>=20
> Hi,
>=20
> I have just noticed a nice new feature: the ability to remove a vdev =
from a pool.
>=20
> I am considering to use it to fix a poorly made pool (sins of youth, =
created in 2012) which right now
> has two raidz1 vdevs (yes, stupid!). I would like to recreate new =
vdevs with more redundance.=20

Sorry, I didn=E2=80=99t notice the =E2=80=9Craidz vdevs not supported=E2=80=
=9D  part :(

Any plans to do it in the future anyway?=20







Borja.