> Depending on exactly how you did it, that should have already happened. > A pool will expand automatically (even in situations where you might not > want it to.) > > Can you show details of your existing configuration that show that it > hasn't expanded?
# fdisk -W - /dev/rdsk/c0d0p0 * Dimensions: * 512 bytes/sector * 63 sectors/track * 255 tracks/cylinder * 12161 cylinders * * systid: [...] * Id Act Bhead Bsect Bcyl Ehead Esect Ecyl Rsect Numsect 12 0 0 1 1 254 63 1023 16065 51102765 131 0 254 63 1023 254 63 1023 51118830 23438835 130 128 254 63 1023 254 63 1023 74557665 35343000 207 0 254 63 1023 254 63 1023 109900665 85465800 # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT rpool 16.8G 12.0G 4.74G 71% ONLINE - tank 40.5G 32.7G 7.79G 80% ONLINE - That last one (tank) is now on c0d0p4, which is the last row in the fdisk output. > I believe (but am not certain) that the PSARC you refer to only has to > do with expanding LUNs. Since you mentioned a "migration", I assume > you didn't expand the existing storage. Is that correct? The "migration" I did was to use "dd" to copy the whole zpool off of the old partition arrangement (while booted from an install CD, zpool not imported at the time) and similarly copied it back after a repartiton that gave this zpool some more space. Now that you mention it, I think it must have filled the space, because I think it was only around 32GB previously. Now it looks like it's taking 40GB out of an available 40.75 GB. Must have expanded, right? (Cool!) Silly me, doubting something might be not automatic in zfs! Thanks, Gordon This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
