There's no need for expansion at that point. The disk already contains a larger partition for rpool, you're just copying files and directories.
Make sure you follow the steps AFTER the data send (GRUB install and file modifications) otherwise your system will be unbootable. Bryan On Sat, 31 Aug 2013 16:22:24 -0400 Harry Putnam <[email protected]> wrote: > Bryan N Iotti <[email protected]> writes: > > > I had an inverse problem, moving rpool to smaller (but faster) disks > > . In the end, I did a send/receive operation after properly formatting > > the receiving drives. > > > > I got the procedure from here: > > https://blogs.oracle.com/mock/entry/how_to_shrink_a_mirrored > > > > and it's been working well. My train of thought is that you could: > > > > - modify your VBox config for the VM by adding one of the larger disks. > > - boot from OI live media > > - do the ZFS send/receive from the old disks to the new ones > > - shutdown the VM > > - remove the old disks from the VM > > - boot from the new ones > > > > I'm not sure about this, but I thought the "autoexpand" feature only > > works on data pools, where you're using the whole disk. > > Well that would be a good thing know. If I followed my plan it would > end up not working... erk. > > So does the send/receive approach allow the rpool to expand into > the larger disc providing the solaris2 partition is the whole > disc? > > > > _______________________________________________ > OpenIndiana-discuss mailing list > [email protected] > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- Bryan N Iotti +39 366 3708436 [email protected]
pgpDR6puL35sS.pgp
Description: PGP signature
_______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
