From owner-freebsd-stable@FreeBSD.ORG Fri Jul 23 15:17:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29E5C106564A for ; Fri, 23 Jul 2010 15:17:54 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id AADB48FC1F for ; Fri, 23 Jul 2010 15:17:53 +0000 (UTC) Received: by fxm13 with SMTP id 13so5574555fxm.13 for ; Fri, 23 Jul 2010 08:17:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=e2BWL7UhCQUgiRffOjnZbSt/xG7THc7rh38xrJ+u2aA=; b=Q6ZFj/JXgm69AfOzohbguW0TSeSvRs0DILfl5AoW8/I8PTDHl89TyA3wZnRLjy1gzX 4/M/iAmsYkFy43c+ee4qojgaGAdQlQK137sqTttI36hwvlppWXV1Cte5x90weR18JAWY qm1YLe17inp3+U4WmDadA1I4kCuuqGguLemz4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Chgapnk4pr4ZveRqYCYmNLE/o2mJKgZM2ELED/6ELzl1kgrWprLRNAab7qi6B17IKZ xwOGOy5Q/B+hiw6d/yjRfL5LxgIJYa6aldVdFDmTyX6mfqwjBBBO7yKRZDcbrTDYOue5 Mr/b8FxVmZSDEaMJCktj+BviHFywe6tvJLY14= MIME-Version: 1.0 Received: by 10.239.155.74 with SMTP id h10mr331846hbc.30.1279898272307; Fri, 23 Jul 2010 08:17:52 -0700 (PDT) Received: by 10.239.173.201 with HTTP; Fri, 23 Jul 2010 08:17:52 -0700 (PDT) In-Reply-To: <718046944.20100723032259@nitronet.pl> References: <4C47B57F.5020309@langille.org> <4C48E695.6030602@langille.org> <718046944.20100723032259@nitronet.pl> Date: Fri, 23 Jul 2010 10:17:52 -0500 Message-ID: From: Tom Evans To: Pawel Tyll Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Dan Langille Subject: Re: Using GTP and glabel for ZFS arrays X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2010 15:17:54 -0000 On Thu, Jul 22, 2010 at 8:22 PM, Pawel Tyll wrote: >> I do not think I can adjust the existing zpool on the fly. =C2=A0I think= I >> need to copy everything elsewhere (i.e the 2 empty drives). =C2=A0Then s= tart >> the new zpool from scratch. > You can, and you should (for educational purposes if not for fun :>), > unless you wish to change raidz1 to raidz2. Replace, wait for > resilver, if redoing used disk then offline it, wipe magic with dd > (16KB at the beginning and end of disk/partition will do), carry on > with GPT, rinse and repeat with next disk. When last vdev's replace > finishes, your pool will grow automagically. > If you do do it like this, be sure to leave the drive you are replacing attached to the array. Otherwise, in a raidz, if you were to suffer a disk failure on one of the other disks whilst replacing/growing the array, your raidz would be badly broken. Other than that, I can thoroughly recommend this method, I had data on 2 x 1.5 TB drives, and set up my raidz initially with 4 x 1.5 TB, 2 x 0.5 TB, copying data off the 1.5 TB drives onto the array and replacing each 0.5 TB drive when done. Cheers Tom