Date: Fri, 6 Aug 2010 02:36:07 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Dan Langille <dan@langille.org> Cc: freebsd-stable@freebsd.org Subject: Re: Where's the space? raidz2 Message-ID: <AANLkTim02yq036gmGE6Cm5DPTuXBM1JjEWk4w3XkaPqM@mail.gmail.com> In-Reply-To: <4C57545F.2050907@langille.org> References: <4C5750A4.7050104@langille.org> <4C57545F.2050907@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 2, 2010 at 4:27 PM, Dan Langille <dan@langille.org> wrote: > On 8/2/2010 7:11 PM, Dan Langille wrote: >> >> I recently altered an existing raidz2 pool from using 7 vdevs of about >> 931G to 1.81TB. In fact, the existing pool used half of each HDD. I then >> wanted to go to using [almost] all of each HDD. >> >> I offline'd each vdev, adjusted the HDD paritions using gpart, then >> replaced the vdev. After letting the resilver occur, I did the next vdev. >> >> The space available after this process did not go up as I expected. I >> have about 4TB in the pool, not the 8 or 9TB I expected. > > This fixed it: > > # zpool export storage > # zpool import storage There's a version of ZFS includes a new *autoexpand* property that could be set on the pool. With that set, the available space will be made available automatically as soon as the last disk in a vdev is replaced. I don't know the exact version or whether it's supported in FreeBSD's port of ZFS. But it will be available at some point. :) -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim02yq036gmGE6Cm5DPTuXBM1JjEWk4w3XkaPqM>