`<div dir="ltr"><div>Hi Michael,</div><div>I had similar problem, after upgrading global zone and rebooting, upgrades in non-global zones failed. Non-global zones had lost their delegated zfs datasets, and was not able to see even zfs they used as root filesystem. I resolved the problem by halting zones, and then upgrading from global zone with "-R" for image directory root. I would also be glad to see recommendations and best practices for upgrading OmniOS with zones.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 6:41 AM, Michael Mounteney <span dir="ltr"><<a href="mailto:gate03@landcroft.co.uk" target="_blank">gate03@landcroft.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">In the global zone I just did:<br>
<br>
# pkg update<br>
<br>
then zlogin to each child zone and<br>
<br>
# pkg update<br>
<br>
there as well. They complained:<br>
<br>
pkg: Unable to clone the current boot environment.<br>
<br>
I rebooted into the new BE then repeated the pkg update in the child<br>
zone with the same result. I then tried to follow the instructions in<br>
<br>
<a href="http://www.thushanfernando.com/index.php/2010/01/14/upgrading-non-global-opensolaris-zone-to-latest-be/" target="_blank">http://www.thushanfernando.com/index.php/2010/01/14/upgrading-non-global-opensolaris-zone-to-latest-be/</a><br>
<br>
but:<br>
<br>
root@world:~# zoneadm -z diener boot<br>
zone 'diener': Unable to unmount the zone's root ZFS dataset<br>
(/zone/diener/root). zone 'diener':<br>
zone 'diener': Is there a global zone process inside the zone root?<br>
zone 'diener':<br>
zone 'diener': The current zone boot environment will remain mounted.<br>
<br>
Just to make it even more fun, it seems there are multiple problems<br>
with services not starting in at least one zone and I've had to revert<br>
to the previous BE.<br>
<br>
This is with bloody_20121228, pkg update to 20130208 (omnios-1) (which<br>
has been working fine since pkg update on about 10 Feb.) so the pkg<br>
update with the problems is omnios-2.<br>
<br>
What have I done wrong ? Something to do with pkg update in child<br>
zones I'm sure.<br>
<br>
Michael.<br>
_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
</blockquote></div><br><div class="gmail_extra">-- </div><div class="gmail_extra"> Regards,</div><div class="gmail_extra"> Sergey Ivanov.</div><div><br></div></div></div>
`