Cindy, Thanks for your reply. The important details may have been buried in my post, I will repeat them again to make it more clear:
(1) This was my boot pool in FreeBSD, but I do not think the partitioning differences are really the issue. I can import the pool to nexenta/opensolaris just fine. Furthermore, this is *no longer* being used as a root pool in nexenta. I purchased an SSD for the purpose of booting nexenta. This pool is used purely for data storage - no booting. (2) I had to hack the code because zpool is forbidding me from adding or replacing devices - please see my logs in the previous post. zpool thinks this pool is a "boot pool" due to the bootfs flag being set, and zpool will not let me unset the bootfs property. So I'm stuck in a situation where zpool thinks my pool is a boot pool because of the bootfs property, and zpool will not let me unset the bootfs property. Because zpool thinks this pool is the boot pool, it is trying to forbid me from creating a configuration that isn't compatible with booting. In this situation, I am unable to add or replace devices without using my hacked version of zpool. I was able to hack the code to allow zpool to replace and add devices, but I was not able to figure out how to set the bootfs property back to the default value. Does this help explain my situation better? I think this is a bug, or maybe I'm missing something totally obvious. Thanks! -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
