Hi,
I am trying to find a way to grow the filesystems in a thumper.
The idea is to take single disks offline and to replace them by bigger
ones.
For this reason, I did run the following test:
mkfile 100m f1
mkfile 100m f2
mkfile 100m f3
mkfile 100m f4
mkfile 100m f5
mkfile 200m F1
mkfile
Hi Jörg,
On Tuesday 02 February 2010 16:40:50 Joerg Schilling wrote:
After that, the zpool did notice that there is more space:
zpool list
NAME SIZE USED AVAILCAP HEALTH ALTROOT
test 476M 1,28M 475M 0% ONLINE -
That's the size already after the initial creation,
Carsten Aulbert carsten.aulb...@aei.mpg.de wrote:
Hi Jörg,
On Tuesday 02 February 2010 16:40:50 Joerg Schilling wrote:
After that, the zpool did notice that there is more space:
zpool list
NAME SIZE USED AVAILCAP HEALTH ALTROOT
test 476M 1,28M 475M 0% ONLINE -
On 02/02/2010 16:09, Joerg Schilling wrote:
Carsten Aulbertcarsten.aulb...@aei.mpg.de wrote:
Hi Jörg,
On Tuesday 02 February 2010 16:40:50 Joerg Schilling wrote:
After that, the zpool did notice that there is more space:
zpool list
NAME SIZE USED AVAILCAP HEALTH ALTROOT
test
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:
#
On 02/02/2010 16:48, Cindy Swearingen wrote:
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.
If you use
* On 02 Feb 2010, Darren J Moffat wrote:
zpool get autoexpand test
This seems to be a new property -- it's not in my Solaris 10 or
OpenSolaris 2009.06 systems, and they have always expanded immediately
upon replacement. In what build number or official release does
autoexpand appear, and
On 02/02/2010 17:29, David Champion wrote:
* On 02 Feb 2010, Darren J Moffat wrote:
zpool get autoexpand test
This seems to be a new property -- it's not in my Solaris 10 or
OpenSolaris 2009.06 systems, and they have always expanded immediately
upon replacement. In what build number or
On Feb 2, 2010, at 9:29 AM, David Champion wrote:
* On 02 Feb 2010, Darren J Moffat wrote:
zpool get autoexpand test
This seems to be a new property -- it's not in my Solaris 10 or
OpenSolaris 2009.06 systems, and they have always expanded immediately
upon replacement. In what build
Hi David,
This feature integrated into build 117, which would be beyond
your OpenSolaris 2009.06. We anticipate this feature will be
available in an upcoming Solaris 10 release.
You can read about it here:
http://docs.sun.com/app/docs/doc/817-2271/githb?a=view
ZFS Device Replacement
* On 02 Feb 2010, Richard Elling wrote:
This behaviour has changed twice. Long ago, the pools would autoexpand.
This is a bad thing, by default, so it was changed such that the expansion
would only occur on pool import (around 3-4 years ago). The autoexpand
property allows you to expand
11 matches
Mail list logo