Thanks .. I stumbled on the export/import as a solution by acciden (see post
below). What confuses me though is that a number of people are reporting that
they do not need to do this step.
See JMCP and others in this thread:
http://www.opensolaris.org/jive/thread.jspa?threadID=50052tstart=0
I
Hi Kava,
Your questions are hard for me to answer without seeing your syntax.
Also, you don't need to futz with slices if you are using whole disks.
I added some add'l information to the zpool replace section
on page 74, here:
http://opensolaris.org/os/community/zfs/docs/zfsadmin.pdf
Note
You do not waste the new space
zfs seems to always work of the lowest device - so when you replace the disks
with larger ones it increases the mirror size to these new drives as thats the
new smallest drive.
This message posted from opensolaris.org
I don't think that is correct. I did it 5 minutes ago and it didn't change the
pool size at all.
Here is what I did:
- create mirrored pool of 2 x 8GB disks
- detach one disk
- attach/replace with 12Gb disk
- detach second disk
- attach/replace with second 12GB disk
After this, the pool was
Kava,
Because of a recent bug, you need to export and import the pool to see
the expanded space after you use zpool replace.
Also, you don't need to detach first. The process would look like this:
# zpool create test mirror 8gb-1 8gb-2
# zpool replace test 8gb-1 12gb-1
# zpool replace test
I finally got this to work, but it did not happen automatically. I needed to
export then re-import the pool to get it to work. Only then did the additional
space appear.
Here is what I did:
- create 4 x 8GB disks and 1 x 4 GB disks
- create RAIDZ pool with 3 x 8GB disks 1 x 4GB
- ignore
Your questions are hard for me to answer without seeing your syntax.
Also, you don't need to futz with slices if you are using whole disks.
I think what he's asking is if it's possible to replace a whole mirror or
RAID-Z vdev in one go. For instance, replacing a small mirror with a bigger
