On Fri, Feb 5, 2010 at 1:30 PM, Bruno Damour <[email protected]> wrote:
> Hello,
> I have just upgraded from b131 to b132 on my home server.
> Everything worked very well : pkg image-update.
> I was just wondering how to upgrade my non-global zones, and was a bit
> worried because I used to run sparse zones and thought I was stuck with full
> upgrade of the zone.
> However I found this thread :
> http://opensolaris.org/jive/thread.jspa?threadID=119286
> and this -u option seemed worth trying.
> It was amazingly swift and simple !!
> # zoneadm -z avalon halt
> # zoneadm -z avalon detach
> # zoneadm -z avalon attach -u
> # zoneadm -z avalon boot
> et voilà zone is running b132 (at least it says so)
>
> The only pb is I have 2 zfs clones :
> tank/zones 1.27G 165G 36K /tank/zones
> tank/zones/avalon 1.27G 165G 24K /tank/zones/avalon
> tank/zones/avalon/ROOT 1.27G 165G 21K legacy
> tank/zones/avalon/ROOT/zbe-1 969M 165G 969M legacy
> tank/zones/avalon/ROOT/zbe-2 333M 165G 994M legacy
>
> What should I do to clean up this ?
beadm destroy <your b131 be name>
All the zones are being cloned as a part of pkg image-update, so that
you would have independent zones for each BE.
--
Regards,
Cyril
_______________________________________________
opensolaris-discuss mailing list
[email protected]
