On 7/02/11 08:22 AM, Mike Gerdts wrote:
...
If I was in the habit of upgrading, creating new BEs, validating
those BEs, then deleting the old ones, why wouldn't the same apply
to zones and thus result in mitigation of the problem you cite
above?
If the old global zone BEs and associated
On Mon 07 Feb 2011 at 07:13PM, Darren Reed wrote:
On 7/02/11 08:22 AM, Mike Gerdts wrote:
...
If I was in the habit of upgrading, creating new BEs, validating
those BEs, then deleting the old ones, why wouldn't the same apply
to zones and thus result in mitigation of the problem you cite
On 2/4/11 10:32 PM, Darren Reed wrote:
On a test system that is using only ZFS, I'm trying to create a zone
but it keeps failing with:
netvirt-d1 ~# zoneadm -z exclusivetestzone1 install
ERROR: the zonepath must be a ZFS dataset.
The parent directory of the zonepath must be a ZFS dataset so that
On Fri, Feb 4, 2011 at 11:32 PM, Darren Reed darren.r...@oracle.com wrote:
On a test system that is using only ZFS, I'm trying to create a zone
but it keeps failing with:
netvirt-d1 ~# zoneadm -z exclusivetestzone1 install
ERROR: the zonepath must be a ZFS dataset.
The parent directory of the
So it would seem this is related to at 7010744 which implies 6726123
needs to be fixed. It could also be a manifestation of 7010102 (if the
submitter means slashes and not spaces.)
Can someone else confirm that?
Or is the problem I've observed different again?
Darren
