From owner-freebsd-fs@FreeBSD.ORG Wed Aug 8 13:08:40 2012 Return-Path: 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 E17411065676 for ; Wed, 8 Aug 2012 13:08:40 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 992B48FC08 for ; Wed, 8 Aug 2012 13:08:40 +0000 (UTC) Received: by yenl7 with SMTP id l7so881094yen.13 for ; Wed, 08 Aug 2012 06:08:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=S//+VjPeX68y5eD6lRGCie3MR4t3nn052ljhuyEIQ+k=; b=GumHmZHGdMHYb1XP7S24GN+WaZsiTl9bozGQBzifsTpr4ZLhoNsHwg1UvW6Qu986A1 ER1BARLkyMjE4wHaC69PAv8YqMrSKkMVcOAMWq9zS7bOwZwy+BzF6k8svR5VMeEasEVe H+3CsAbLqjBXrYfMs7eL4Nk64XTv7Nm5qp6HrbyIV0I4fv2Eh5o/+VlpAX1MFJasghN7 A9SQVNIQp19utolsLzu0Cl4HkMlmzXNZasVR2PQs4LpJTyrdUsHev69gBxIWhK+JhB8A s1uzxcbFp59qKo5feYQQy1SbehGTYkLj08jBL4Gt07qYgApX3HYvFkimefn8euuiJ6fk 23dw== Received: by 10.50.87.198 with SMTP id ba6mr892451igb.22.1344431313831; Wed, 08 Aug 2012 06:08:33 -0700 (PDT) Received: from AL-MB-MWS0001.mediacomcorp.com ([173.156.229.158]) by mx.google.com with ESMTPS id dk7sm4796139igb.10.2012.08.08.06.08.32 (version=SSLv3 cipher=OTHER); Wed, 08 Aug 2012 06:08:33 -0700 (PDT) Date: Wed, 8 Aug 2012 08:08:29 -0500 From: Chuck Burns To: freebsd-fs@freebsd.org Message-Id: <20120808080829.534e6e16.break19@gmail.com> In-Reply-To: References: <201208080424.q784OEfY051025@gw.catspoiler.org> X-Mailer: Sylpheed 3.1.3 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ZFS questions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2012 13:08:41 -0000 On Wed, 08 Aug 2012 10:05:10 +0200 "Ronald Klop" wrote: > > I'm slowly accumulating the drives over time for both budgetary reasons > > and to also try to reduce the chances of multiple near-simultaneous > > failures of drives from the same manufacturing batch. I'd like to get > > the array up and running before I have all the drives, but unfortunately > > ZFS doesn't allow new drives to be added to an existing raidz vdev to > > increase its capacity. I do have some smaller drives and I was thinking > > about pairing those up with gconcat or gstripe and configuring the ZFS > > pool with the concatenated/striped pairs. I know this isn't > > recommended, but it seems to me like zpool create would accept this. > > What concerns me is happens on reboot when ZFS goes searching for all of > > the components of its pool. Will it stumble across its metadata on the > > first of the two concatenated pairs and try to add that individual drive > > to the pool instead of the pair? > > I don't know. Somebody else might answer this. > > Ronald. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Wouldn't it work to just use 1 new, large drive, along with the rest of the smaller drives, simply replacing them with the large drives as you get them? the -size- of the vdevs can change.. and from my limited testing, it seems you can upgrade space, not by adding more drives, but by replacing existing drives in the vdev with larger ones, then resilvering.. -- Chuck Burns