[indiana-discuss] beadm activate issue while upgrade to snv_94

[Mike Gerdts]

On Tue, Jul 29, 2008 at 8:43 PM, Praveen Kumar <praveen at sun.com> wrote:
> I am running snv_93. I tried upgrading to snv_94. Even though I can use
> 'pkg image-update' on the image, I did the following so that I can
> choose the name of the BE instead of getting some arbitrary number suffix.
>
> $ pfexec beadm create opensolaris-snv_94
> $ pfexec beadm mount opensolaris-snv_94 /mnt
> $ pfexec pkg -R /mnt image-update -v
> $ pfexec beadm unmount opensolaris-snv_94
> $ pfexec beadm activate opensolaris-snv_94
> beadm: Unable to activate opensolaris-snv_94
>
> Is there a chance that this is a bug?

I bet you are running into the same thing I have whined about, but
have been told it's not a bug.

http://mail.opensolaris.org/pipermail/indiana-discuss/2008-June/007121.html

Try

pfexec truss beadm activate opensolaris-snv_94

And look for ENOSPC.  If it is the same thing, read on.

As I just posted to caiman-discuss and pkg-discuss, it seems as though
the only way to have a good deal of certainty that you will be able to
create, update, and activate a new boot environment, you need to be
sure that you have 2x the amount of free space as the amount of space
used by your active boot environment.

http://mail.opensolaris.org/pipermail/caiman-discuss/2008-July/004739.html

I see this as a bug or at least a really important RFE related to how
"zfs promote" works.

-- 
Mike Gerdts
http://mgerdts.blogspot.com/