From owner-freebsd-fs@FreeBSD.ORG Mon Nov 30 20:33:10 2009 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 062AD106566B for ; Mon, 30 Nov 2009 20:33:10 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 87E8E8FC0A for ; Mon, 30 Nov 2009 20:33:09 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id l26so1505691fgb.13 for ; Mon, 30 Nov 2009 12:33:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=x2yyCHCgUdA3rHLKwzpXneexlDnzeBDNJw04wt8uRYI=; b=Wm3FjDfZMXEHwcz2I1fDrtGbF20dRiXBqXIp/t33l2aQz2lA+rAJgZXTBYL1BCnM6g gawDtXRqjm0QKmIuV4nvFdT/BYZUEOBL+Ff47B4QHOawr1+3mVyaqfYfP37B8cWB7QdS QiA1F/cIL4xz8RAFoLrtP7qG7xqt9Ahq7RPfk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mcl/JRyhrFsBIqon3XAYnw9km2ZK8MNorBUNdPb3T6jBYvVuQlErqQ+xSLXry7Yrfm Io3STrbjQV9m9+fNQ3xLaPGnxYHtPMItFwAq2LnXzTi9UQktn9CZUSv31/DO2RxYoFsB RubfF+OpaooutildQxZmrTCQM13y1m5+/FK6I= MIME-Version: 1.0 Received: by 10.216.89.5 with SMTP id b5mr1528725wef.143.1259613188404; Mon, 30 Nov 2009 12:33:08 -0800 (PST) In-Reply-To: <2ae8edf30911300425g4026909bm9262f6abcf82ddcd@mail.gmail.com> References: <2ae8edf30911300120x627e42a9ha2cf003e847d4fbd@mail.gmail.com> <4B139AEB.8060900@jrv.org> <2ae8edf30911300425g4026909bm9262f6abcf82ddcd@mail.gmail.com> Date: Mon, 30 Nov 2009 15:33:08 -0500 Message-ID: <5f67a8c40911301233s46a2818at9051c4ebbacf7e25@mail.gmail.com> From: Zaphod Beeblebrox To: Wiktor Niesiobedzki Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs Subject: Re: ZFS guidelines - preparing for future storage expansion 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: Mon, 30 Nov 2009 20:33:10 -0000 On Mon, Nov 30, 2009 at 7:25 AM, Wiktor Niesiobedzki wrote: > 2009/11/30 James R. Van Artsdalen : > > Wiktor Niesiobedzki wrote: > >> do I need to do something more, to get new space used by > >> RAIDZ? > > > > Export the pool, the import it. Adding a vdev is done right away, but > > increasing the size of a vdev (as you did) only happens on import. > > > > That did the trick, thanks :-) Cool thing! :-) > Wasn't a reboot also an option (which might disturb active NFS mounts less)? I moved from 5x 750G to 5x 1.5T disks this way earlier this year. It takes a _long_ time. resilvering 750g (they were about 98% full when I did this) onto the 1.5T disks took about 12 hours each. With work and sleep and other distractions, it took most of a week to perform the upgrade. And keep in mind that while you're upgrading, you're vulnerable to data loss (no more replicas). I suppose RAIDZ2 would make that safer, but more costly. This form of upgrade is a cool feature --- in the end the "cost" of running a home RAID array is the cost of the electricity ... and I'm pretty sure the draw of the 1.5T drives is very similar to the 750G drives. I'm not sure I see this feature being used a lot in production, tho. It's a pretty high stress on the array for a long time.