On 06/ 2/11 07:03 AM, Matt Keenan wrote:
Hi,Can I get a code review for bug : 7048223 Multi-pool installed data pools need to be imported on first boot http://monaco.sfbay.sun.com/detail.jsf?cr=7048223 Webrev: http://cr.opensolaris.org/~mattman/bug-7048223/ Some background : With the integration of CUD based AI installations, Multi-Pool support has been added. All pools other than the root pool (data pools) created during an AI install do not get automatically imported when the installed client boots. This is because they are not created within the newly installed BE. Not importing these pools on first boot could potentially have catastrophic effects, in scenarios where dump/swap volumes were being created on a data pool instead of the root pool, or where user account home directories are being created on a non root pool, These datasets would not be available on boot if the pools are not imported. I've spent considerable time testing various scenarios to try and get this to happen, and initiated a discussion on zfs-discuss to determine the easiest means of achieving this. Usage of zpool create/import with -R altroot and -o cachefile options were mentioned as potential solutions, however these have proved unsuccessful, due to hostid issues.
This info should be reflected in the CR, please, as the last note there says that was the direction we were going. What gets in the way of retaining the hostid into the installed environment? It would seem much preferable to avoid adding all this mechanism, not to mention the issue that the service is being split for the unconfig work and this would entail yet further changes.
Dave _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
