Guido Berhoerster wrote: > * Ethan Quach <[EMAIL PROTECTED]> [2008-11-24 21:14]: > >> This shouldn't be happening on a freshly installed RC2 >> system. If you fresh install RC2 and create zones, you >> should be able to image-update just fine (though the zones >> you created won't be udpated; you have to detach and >> re-attach them when you boot the updated BE. >> > > It was definitely a clean install of RC2 I made for testing > purposes. The problem is that I had already deleted the zone. I > created and installed a new zone and cannot reproduce the error > any more creating BEs seems to work fine for now. > > >>> Diagnostic output follows: >>> >>> # BE_PRINT_ERR=true beadm create testbe >>> be_get_uuid: failed to get uuid property from BE root dataset user >>> properties. >>> be_copy_zones: failed to snapshot zone BE >>> (rpool/export/zones/testzone/ROOT/[EMAIL PROTECTED]): dataset is busy >>> >>> >> This is a zfs bug and seems to happen randomly with zones. >> We saw it a couple times during development of ipkg zones >> support in the boot environment code. Its filed as 6462803 >> >> http://bugs.opensolaris.org/view_bug.do?bug_id=6462803 >> >> >> Does the workaround work for you? >> > > Unfortunately I cannot reproduce it, I will try it and report > back if I encounter this again. > What does the other error message ("be_get_uuid: failed to > get uuid property from BE root dataset user properties.") mean, I > still get that, though it's not fatal? >
those are harmless; they just happen to come out with the debug flag set on. (I think we mount the new BE right after creating it but before setting the uuid on it so the mount code complains a little bit thanks, -ethan _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
