I just ran into this problem (strangely, only on one zone on one machine). None
of the above fixed it.
However, what I finally discovered was that the parentbe UUID attribute of both
the older (pre-upgrade) and the newer (post-upgade) non-global zone BE was set
to the UUID of the *current* global BE. That's the cause of the "ERROR:
multiple active datasets." The zoneadm command can't tell which of the zone's
datasets corresponds to the current global BE. I'm not sure how this happened,
but it was definitely a failure during the 'pkg image-update' process updating
to snv_151a.
# zfs get -r org.opensolaris.libbe:parentbe rpool/zones/tersk/ROOT
NAME PROPERTY
VALUE SOURCE
rpool/zones/tersk/ROOT
org.opensolaris.libbe:parentbe - -
rpool/zones/tersk/ROOT/zbe
org.opensolaris.libbe:parentbe 1cceaa0c-a93c-6ef3-a777-feeb54743a77 local
rpool/zones/tersk/ROOT/zbe-1
org.opensolaris.libbe:parentbe 1cceaa0c-a93c-6ef3-a777-feeb54743a77 local
Once I discovered that, the fix was simple. I found the correct, older global
zone dataset UUID:
# zfs get org.opensolaris.libbe:uuid rpool/ROOT/snv_134
NAME PROPERTY VALUE
SOURCE
rpool/ROOT/snv_134 org.opensolaris.libbe:uuid
4315c502-a5cd-4a61-9ef6-ab593f2be0fb local
And then set the older non-global zone (tersk) parentbe to that value:
# zfs set org.opensolaris.libbe:parentbe=4315c502-a5cd-4a61-9ef6-ab593f2be0fb
rpool/zones/tersk/ROOT/zbe
Everything came right up after that.
Hope this helps,
- Geoff
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
