zfs discuss - Nov 2009 - zpool not growing after drive upgrade

So I''ve finally finished swapping out my old 300GB drives.  The end
result
is one large raidz2 pool. 10+2 with one hot spare.

The drives are:
7x500GB
4x1TB
2x1.5TB

One of the 1.5TB is the hot spare.  zpool list is still showing capacity of
3.25TB (the 1TB drives replaced 300GB drives).  I''ve tried exporting
and
importing the pool, and it doesn''t make a difference.

NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
fserv  3.25T  2.73T   532G    84%  ONLINE  -


--Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091112/e044918e/attachment.html>

Hi Tim,

In a pool with mixed disk sizes, ZFS can use only the amount of disk
space that is equal to the smallest disk and spares aren''t included in
pool size until they are used.

In your RAIDZ-2 pool, this is equivalent to 10 500 GB disks, which
should be about 5 TBs.

I think you are running a current Nevada release. Did you try setting
the autoexpand property to on?

See the example below, I created a RAIDZ-2 pool with 2 68 GB disks and 1 
136 GB disk. I replaced the 2 68 GB disks with 2 136 GB disks and set
autoexpand to on. My pool space increased from 204 GB to 410 GB on
Nevada, build 127, which sounds about right. The autoexpand property
integrated into build 117.

Cindy

# zpool create test raidz2 c2t2d0 c2t3d0 c0t5d0
invalid vdev specification
use ''-f'' to override the following errors:
raidz contains devices of different sizes
# zpool create -f test raidz2 c2t2d0 c2t3d0 c0t5d0
# zpool list test
NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
test   204G   286K   204G     0%  1.00x  ONLINE  -
# zpool replace test c2t2d0 c0t6d0
# zpool replace test c2t3d0 c0t7d0
# zpool list test
NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
test   204G   464K   204G     0%  1.00x  ONLINE  -
# zpool set autoexpand=on test
# zpool list test
NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
test   410G   423K   410G     0%  1.00x  ONLINE  -



On 11/12/09 14:10, Tim Cook wrote:
> So I''ve finally finished swapping out my old 300GB drives.  The
end
> result is one large raidz2 pool. 10+2 with one hot spare.
> 
> The drives are:
> 7x500GB
> 4x1TB
> 2x1.5TB
> 
> One of the 1.5TB is the hot spare.  zpool list is still showing capacity 
> of 3.25TB (the 1TB drives replaced 300GB drives).  I''ve tried
exporting
> and importing the pool, and it doesn''t make a difference.
> 
> NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
> fserv  3.25T  2.73T   532G    84%  ONLINE  -
> 
> 
> --Tim
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Thu, Nov 12, 2009 at 4:05 PM, Cindy Swearingen
<Cindy.Swearingen at sun.com>wrote:
> Hi Tim,
>
> In a pool with mixed disk sizes, ZFS can use only the amount of disk
> space that is equal to the smallest disk and spares aren''t
included in
> pool size until they are used.
>
> In your RAIDZ-2 pool, this is equivalent to 10 500 GB disks, which
> should be about 5 TBs.
>
> I think you are running a current Nevada release. Did you try setting
> the autoexpand property to on?
>
> See the example below, I created a RAIDZ-2 pool with 2 68 GB disks and 1
> 136 GB disk. I replaced the 2 68 GB disks with 2 136 GB disks and set
> autoexpand to on. My pool space increased from 204 GB to 410 GB on
> Nevada, build 127, which sounds about right. The autoexpand property
> integrated into build 117.
>
> Cindy
>
> # zpool create test raidz2 c2t2d0 c2t3d0 c0t5d0
> invalid vdev specification
> use ''-f'' to override the following errors:
> raidz contains devices of different sizes
> # zpool create -f test raidz2 c2t2d0 c2t3d0 c0t5d0
> # zpool list test
> NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
> test   204G   286K   204G     0%  1.00x  ONLINE  -
> # zpool replace test c2t2d0 c0t6d0
> # zpool replace test c2t3d0 c0t7d0
> # zpool list test
> NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
> test   204G   464K   204G     0%  1.00x  ONLINE  -
> # zpool set autoexpand=on test
> # zpool list test
> NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
> test   410G   423K   410G     0%  1.00x  ONLINE  -
>
>
>
That did it, thank you.  Didn''t the pools expand automatically on an
export/import before, or am I crazy?  I swore that''s all I had to do
last
time.

--Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20091112/4ef047b0/attachment.html>

Previous behavior was hard to predict. :-)

It worked for a while, then a bug prevented it from working so that you
had to export/import the pool to see the expanded space.

The export/import thing was a temporary workaround until the autoexpand
features integrated.


cs

On 11/12/09 15:23, Tim Cook wrote:
> 
> 
> On Thu, Nov 12, 2009 at 4:05 PM, Cindy Swearingen 
> <Cindy.Swearingen at sun.com <mailto:Cindy.Swearingen at
sun.com>> wrote:
> 
>     Hi Tim,
> 
>     In a pool with mixed disk sizes, ZFS can use only the amount of disk
>     space that is equal to the smallest disk and spares aren''t
included in
>     pool size until they are used.
> 
>     In your RAIDZ-2 pool, this is equivalent to 10 500 GB disks, which
>     should be about 5 TBs.
> 
>     I think you are running a current Nevada release. Did you try setting
>     the autoexpand property to on?
> 
>     See the example below, I created a RAIDZ-2 pool with 2 68 GB disks
>     and 1 136 GB disk. I replaced the 2 68 GB disks with 2 136 GB disks
>     and set
>     autoexpand to on. My pool space increased from 204 GB to 410 GB on
>     Nevada, build 127, which sounds about right. The autoexpand property
>     integrated into build 117.
> 
>     Cindy
> 
>     # zpool create test raidz2 c2t2d0 c2t3d0 c0t5d0
>     invalid vdev specification
>     use ''-f'' to override the following errors:
>     raidz contains devices of different sizes
>     # zpool create -f test raidz2 c2t2d0 c2t3d0 c0t5d0
>     # zpool list test
>     NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
>     test   204G   286K   204G     0%  1.00x  ONLINE  -
>     # zpool replace test c2t2d0 c0t6d0
>     # zpool replace test c2t3d0 c0t7d0
>     # zpool list test
>     NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
>     test   204G   464K   204G     0%  1.00x  ONLINE  -
>     # zpool set autoexpand=on test
>     # zpool list test
>     NAME   SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
>     test   410G   423K   410G     0%  1.00x  ONLINE  -
> 
> 
> 
> That did it, thank you.  Didn''t the pools expand automatically on
an
> export/import before, or am I crazy?  I swore that''s all I had to
do
> last time.
> 
> --Tim