Bug 3783 - Install will fail if ZFS pool 'rpool' was imported
: Install will fail if ZFS pool 'rpool' was imported
Status: CAUSEKNOWN
Product: installer
library
: unspecified
: Other OpenSolaris
: P4 normal (vote)
: 2010.1H
Assigned To: installer watcher
:
:
: reviewed-2009.06
:
: 5734
:
  Show dependency treegraph
 
Reported: 2008-10-08 04:28 UTC by Jan Damborsky
Modified: 2009-11-02 09:48 UTC (History)
2 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Jan Damborsky 2008-10-08 04:28:44 UTC
If a ZFS pool named "rpool" is already present because it was manually imported
by the user during current boot of live CD, the install process will fail
immediately, the last message in the installation log being:

Root pool rpool exists, we can't proceed with the installation.

Please see bug 1771 for background and more details.
Comment 1 Dave Miner 2008-11-20 11:48:45 UTC
See also bug 5270.
Comment 2 Jan Damborsky 2009-05-21 05:16:14 UTC
Starting build 88, exporting the rpool no longer makes it unbootable. Based on
this, it should be again investigated, if 'zpool export rpool' might be
suitable
solution to address this problem.
Comment 3 Mark Fenwick 2009-05-22 12:42:36 UTC
Although it does not say so in the description, I'm led to believe that this
functionality allowed the installer to detect existing ZFS pools and prevented
it from accidentally installing over a working installation. Now that the
reason for its removal has been fixed, it would be nice to have this feature
back.
Comment 4 Jan Damborsky 2009-10-06 14:11:27 UTC
To be more precise, install will fail if ZFS pool with name 'rpool' is seen
(visible by 'zpool list' command) and user property
'org.opensolaris.caiman:install' was either not created or set to 'ready'.
If this property is set to 'busy', it indicates that 'rpool' contains
incomplete
OpenSolaris instance and pool is safely destroyed in that case.