solarg wrote:
Evan Layton wrote:
be_get_uuid: failed to get uuid property from BE root dataset user
properties.
be_copy_zones: failed to snapshot zone BE
(rpool/export/catalogue4/ROOT/z...@zbe-1): dataset is busy
be_copy: failed to process zones
be_copy: destroying partially created boot environment
pkg: unable to create BE None
pkg: image-update cannot be done on live image
There was a ZFS issue that has now been fixed that could cause the
dataset to report that it was busy when attempting to take a snapshot.
It appears that this may be what you are hitting. To work around this
try making sure all your zones are in the running state so that their
datasets are mounted. Then try to do a beadm create of a new BE and
see if it is able to create a new BE. If it can then you should be OK
to try the image-update.
what do you think of that:
- mounting the zones without booting them
- create a BE
he...@ultra20:~$ zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native
shared
1 catalogue4 mounted /export/catalogue4 ipkg
shared
2 toto mounted /export/toto ipkg
shared
3 master mounted /export/master ipkg
shared
he...@ultra20:~$ BE_PRINT_ERR=true pfexec beadm create testbe
be_get_uuid: failed to get uuid property from BE root dataset user
properties.
he...@ultra20:~$ beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
opensolaris-3 - - 108.81M static 2008-11-12 13:58
opensolaris-4 NR / 15.67G static 2008-12-12 11:23
testbe - - 369.5K static 2009-05-29 14:24
is it sufficient? can i trust it?
gerard
Yes you can trust it. That uuid message is a known bug (7877) in the
debug output but isn't an indication of an actual error.
-evan
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
