On 2012-12-03 20:35, Heiko L. wrote:
I've already tested:
beadm create -p $dstpool $bename
beadm list
zpool set bootfs=$dstpool/ROOT/$bename $dstpool
beadm activate $bename
beadm list
init 6
- result:
root@opensolaris:~# init 6
updating //platform/i86pc/boot_archive
updating //platform/i86pc/amd64/boot_archive
Hostname: opensolaris
WARNING: pool 'rpool1' could not be loaded as it was last accessed by another
system (host: opensolaris hostid: 0xc08358). See:
http://www.sun.com/msg/ZFS-8000-EY
...hang...
- seen to be a bug...
You wrote you use opensolaris - if literally true, this is quite old
and few people would say definitely which bugs to expect in which
version.
I might guess (hope) your ultimate goal by increasing the disk is to
upgrade the VM to a more current build, like OI or Sol11?
Still, while booted from the old rpool, after activating the new one,
you could also "zpool export rpool1" in order to mark it as cleanly
exported and not potentially held by another OS instance. This should
allow to boot from it, unless some other bug steps in...
//Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
