Hi Alex,
The SXCE Admin Guide is generally up-to-date on docs.sun.com.
The section that covers the autoreplace property and default
behavior is here:
http://docs.sun.com/app/docs/doc/817-2271/gazgd?a=view
Thanks,
Cindy
On 12/07/09 14:50, Alexandru Pirvulescu wrote:
Thank you. That fixed the problem.
All the tutorials on Internet didn't mention autoexpand.
Again, thank you everybody for the quick reply and solving my problem.
Alex
On Dec 7, 2009, at 11:48 PM, Ed Plese wrote:
On Mon, Dec 7, 2009 at 3:41 PM, Alexandru Pirvulescu <sigx...@gmail.com> wrote:
I've read before regarding zpool size increase by replacing the vdevs.
The initial pool was a raidz2 with 4 640GB disks.
I've replaced each disk with 1TB size by taking it out, inserting the new disk,
doing cfgadm -c configure on port and zpool replace bigpool c6tXd0
The problem is the zpool size is the same (2.33TB raw) as seen below:
# zpool list bigpool
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
bigpool 2.33T 1.41T 942G 60% 1.00x ONLINE -
It should be ~ 3.8-3.9 TB, right?
An autoexpand property was added a few months ago for zpools. This
needs to be turned on to enable the automatic vdev expansion. For
example,
# zpool set autoexpand=on bigpool
Ed Plese
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
