Brandon,
Using beadm to migrate your BEs to another root pool (and then
performing all the steps to get the system to boot) is different
than just outright renaming your existing root pool on import.
Since pool renaming isn't supported, I don't think we have identified
all the boot/mount-at-boot components that need to be changed.
Cindy
On 05/03/10 18:34, Brandon High wrote:
On Mon, May 3, 2010 at 9:13 AM, Cindy Swearingen
<cindy.swearin...@oracle.com> wrote:
Renaming the root pool is not recommended. I have some details on what
actually breaks, but I can't find it now.
Really? I asked about using a new pool for the rpool, and there were
some comments that it works fine. In fact, you'd suggested using beadm
to move the BE to the new pool.
On x86, grub looks at the findroot command, which checks
/rpool/boot/grub/bootsign/ (See
http://docs.sun.com/app/docs/doc/819-2379/ggvms?a=view)
The zpool should have the bootfs property set (although I've had it
work without this set). (See
http://docs.sun.com/app/docs/doc/819-2379/ggqhp?l=en&a=view)
To answer Richard's question, if you have to rename a pool during
import due to a conflict, the only way to change it back is to
re-import it with the original name. You'll have to either export the
conflicting pool, or (if it's rpool) boot off of a LiveCD which
doesn't use an rpool to do the rename.
-B
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
