Can't expand zfs pool with new devices

Colin B.

unread,

Nov 6, 2009, 11:52:46 AM11/6/09

to

So I've got a RAIDZ dataset, consisting of six 9GB drives in a multipack.
One by one, I offline and replace them with 18GB drives. Unfortunately,
the size didn't increase after the last resilvering, as I thought it would.
Is there anything I can do to 'kick' the zpool, and make it recognise that
it now has double the space?

This is on Solaris 10 05/09, with zpool version 10.

Cheers,
Colin

Casper H.S. Dik

unread,

Nov 6, 2009, 12:45:25 PM11/6/09

to

"Colin B." <cbi...@somewhereelse.shaw.ca> writes:

>So I've got a RAIDZ dataset, consisting of six 9GB drives in a multipack.
>One by one, I offline and replace them with 18GB drives. Unfortunately,
>the size didn't increase after the last resilvering, as I thought it would.
>Is there anything I can do to 'kick' the zpool, and make it recognise that
>it now has double the space?

I'm afraid that you need to remove or export/import the pool.
(Limitation later fixed in OpenSolaris)

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

cindy

unread,

Nov 6, 2009, 12:46:54 PM11/6/09

to

Hi Colin,

You should be able to export and import the pool to see the expanded
pool size. A reboot might work too.

This issue is fixed in the Solaris Nevada release, build 117.

Cindy

Colin B.

unread,

Nov 6, 2009, 1:19:49 PM11/6/09

to

Casper H.S. Dik <Caspe...@sun.com> wrote:
> "Colin B." <cbi...@somewhereelse.shaw.ca> writes:
>
>>So I've got a RAIDZ dataset, consisting of six 9GB drives in a multipack.
>>One by one, I offline and replace them with 18GB drives. Unfortunately,
>>the size didn't increase after the last resilvering, as I thought it would.
>>Is there anything I can do to 'kick' the zpool, and make it recognise that
>>it now has double the space?
>
> I'm afraid that you need to remove or export/import the pool.
> (Limitation later fixed in OpenSolaris)

Ah, my mistake. I got the impression that expansion was automatic until
a recent OpenSolaris build, which added "autoexpand" as a settable flag.

Oh well. Easy enough to drop this box to single-user and export/import.

Thanks Casper and Cindy,
Colin

chuckers

unread,

Nov 8, 2009, 6:35:16 PM11/8/09

to

I am not quite clear on what a zpool export command will do.

When you do an export, do you have to have a place for the data to go
or is
it just saying that the data is going offline for a while and you
shouldn't touch it?

Likewise, when you do the zpool import command, it will say here is
some data coming back
on line, and oh, hey, look it is on disks that are now *this* size
which was larger than before?

Is it possible to export root pools?

Casper H.S. Dik

unread,

Nov 9, 2009, 4:07:56 AM11/9/09

to

chuckers <chuck...@gmail.com> writes:

>I am not quite clear on what a zpool export command will do.

A "zpool export" command will cause the devices to unmount and
the kernel "forgets" the zpool.

Clearly, that won't work for rpools.

>When you do an export, do you have to have a place for the data to go
>or is
>it just saying that the data is going offline for a while and you
>shouldn't touch it?

No. Just "zpool import" and you get the files again.

>Is it possible to export root pools?

Nope.

Just use "reboot"; it's pretty much the same as "export; import".