From owner-freebsd-fs@FreeBSD.ORG  Wed Sep  1 01:20:10 2010
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 A030A10656C2
	for <freebsd-fs@freebsd.org>; Wed,  1 Sep 2010 01:20:10 +0000 (UTC)
	(envelope-from artemb@gmail.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
	[209.85.212.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 4FD478FC15
	for <freebsd-fs@freebsd.org>; Wed,  1 Sep 2010 01:20:09 +0000 (UTC)
Received: by vws7 with SMTP id 7so7052772vws.13
	for <freebsd-fs@freebsd.org>; Tue, 31 Aug 2010 18:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:sender:received
	:in-reply-to:references:date:x-google-sender-auth:message-id:subject
	:from:to:cc:content-type:content-transfer-encoding;
	bh=C75rNDr+pyZ1zaK/HLsEkKEA4A+FviQd7T/lk9QGdL4=;
	b=VwJcI2YoaQ0KHqg5ywycgCCSQJsSHT5GSeMKh7yvPDppEXSXUs3Xv246w1qxOXYZTT
	C6ObbjWa26yqVqbw0iRQ8FuOgaVkstWg3ww2tqXKbQhiZ4I+QN4dWktt2W9AYqSVkNKr
	cl6ZfBMl7/buu9QiayJRXVmtUmOYbFQOWUjws=
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=d0VsnC3q1JfiDPSLVcy5F9yGleeZ6BTXr/0IX2p6JChMdCeHMqw6Q11Dk2iPlYr5Ev
	7e9YJpA4OCTANdoOfK/oPHgaeOttmUcA5GTaHkLvcy8Lfx+DQch6OSoV4tW7X4x+roiW
	Wfgc1TXE/fAqeReZ8LPv0qcaQPW7bp3RPM/Xo=
MIME-Version: 1.0
Received: by 10.220.162.148 with SMTP id v20mr4745353vcx.36.1283304009372;
	Tue, 31 Aug 2010 18:20:09 -0700 (PDT)
Sender: artemb@gmail.com
Received: by 10.220.66.227 with HTTP; Tue, 31 Aug 2010 18:20:09 -0700 (PDT)
In-Reply-To: <4C7D9BF1.9010102@dannysplace.net>
References: <4C7D9BF1.9010102@dannysplace.net>
Date: Tue, 31 Aug 2010 18:20:09 -0700
X-Google-Sender-Auth: JxvwZc-Xr424VlCTt_0gWfoXHjY
Message-ID: <AANLkTin6pXhP7Bsu9H8j3eO=Mkr+o-vuCt0i6NhePo0s@mail.gmail.com>
From: Artem Belevich <fbsdlist@src.cx>
To: fbsd@dannysplace.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-fs <freebsd-fs@freebsd.org>
Subject: Re: How is data written to a pool with multiple VDevs
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: Wed, 01 Sep 2010 01:20:10 -0000

On Tue, Aug 31, 2010 at 5:18 PM, Danny Carroll <fbsd@dannysplace.net> wrote=
:
...
> My question is: =A0Since the data will initially be on only one of the
> raidz vdevs, when I add the second one, will ZFS re-organise the data on
> the whole pool to be efficient or will I end up with only new data being
> striped.

No, I believe ZFS will not reorganize the data that's already written.
However, ZFS will make an attempt to spread the data across both vdev
once both are available.

> If that is the case then I will try and find a way to build the new
> array fully on a temporary machine first before copying the data.

I guess once you've added second vdev and provided that you have
enough space left, you can try copying your dataset once again. New
copy will be spread across both vdevs.

--Artem