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

[Mike Gerdts]

On Wed, Jul 30, 2008 at 10:25 AM, Dave Miner <Dave.Miner at sun.com> wrote:
> Mike Gerdts wrote:
>> The essence of the bug that I believe exists is that an unreasonable
>> amount of free space is required to do a promote.  I don't believe
>> that there is any point in time or failure mode that actually requires
>> this space - I think it is an erroneous check in the zfs promote code
>> path.  Then again, I don't know that code so others are certainly
>> better placed to provide an explanation as to why it is required.
>
> I think part of the problem here is that we may be excessively aggressive in
> promoting BE's.  With the current behavior you end up with all snapshots
> attached to the most recent BE, which exacerbates the issue, I think.  Needs
> some investigation to determine if we can be smarter about this.
>
> Dave
>

In order to free up the space from that initial installation you will
have to promote one of the others.  It is probably better to see the
problem right away rather than after you have potentially
image-updated several times.  This goes along the same lines as crash
when I dereference a null pointer rather than doing the 0 at 0 trick to
push the error off to sometime later when the problem is much more
difficult to figure out.

If you find out right away, you may be able to do something like:

beadm destroy newbe
rm /var/crash/*/*
find /var/tmp -type f -mtime +30 | xargs rm -f
pkg image-update

If you find out later, you need to mirror to a bigger disk (which
bricked the system last time I tried) or backup+destroy+restore.

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