Hi Joerg,
Eabling the autoexpand property after the disk replacement is complete
should expand the pool. This looks like a bug. I can reproduce this
issue with files. It seems to be working as expected for disks.
See the output below.
Thanks, Cindy
Create pool test with 2 68 GB drives:
# zpool create test c2t2d0 c2t3d0
# zpool list test
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
test 136G 126K 136G 0% 1.00x ONLINE -
# zfs list test
NAME USED AVAIL REFER MOUNTPOINT
test 73.5K 134G 21K /test
Replace 2 68 GB drive with 136 GB drives and set autoreplace:
# zpool replace test c2t2d0 c0t8d0
# zpool replace test c2t3d0 c0t9d0
# zpool list test
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
test 136G 166K 136G 0% 1.00x ONLINE -
# zfs list test
NAME USED AVAIL REFER MOUNTPOINT
test 90K 134G 21K /test
# zpool set autoexpand=on test
# zpool list test
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
test 273G 150K 273G 0% 1.00x ONLINE -
On 02/02/10 09:22, Joerg Schilling wrote:
Darren J Moffat <darr...@opensolaris.org> wrote:
Did yours grow?
If yes, what did I do wrong?
What does this return:
zpool get autoexpand test
zpool get autoexpand test
NAME PROPERTY VALUE SOURCE
test autoexpand off default
Thank you for this hint!
BTW: setting autoexpand later did not help but setting it before
I replaced the "media" resulted in a grown zpool and zfs.
Jörg
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
