[indiana-discuss] BE problem

[Aubrey Li]

On Tue, Jun 10, 2008 at 12:41 AM, Ethan Quach <ethan.quach at sun.com> wrote:
>
>
> Aubrey Li wrote:
>>
>> Hi folks,
>>
>> I'm just starting to learn BE.
>> 1) BE can't be activated
>> # beadm list
>>
>> BE          Active Active on Mountpoint Space
>> Name               reboot               Used
>> ----        ------ --------- ---------- -----
>> opensolaris yes    yes       legacy     3.27G
>>
>> # beadm create test
>> # beadm list
>>
>> BE          Active Active on Mountpoint Space
>> Name               reboot               Used
>> ----        ------ --------- ---------- -----
>> test        no     no        -          66.5K
>> opensolaris yes    yes       legacy     3.27G
>>
>> # beadm activate test
>> beadm: Unable to activate test
>>
>> Did I do anything wrong or did I miss anything?
>
> Doesn't look like you did anything wrong.  What's the
> space usage of your pool?  The only thing I can think of
> is that the zfs promotion of the "test" BE dataset(s)
> failed because of lack of space.
>
> (1816 is being worked on to get better error messages
> from beadm).
>
I'm working on the virtualbox, zpool list told me available space
is 1.52G, If it is not enough, then BE is so bigger than my expectation, :-)

>>
>> 2) BE list after pkg image-update to SNV_90
>> $ beadm list
>>        BE            Active Active on Mountpoint     Space
>>        Name                 reboot                   Used
>>        ----          ------ --------- ----------     -----
>>        opensolaris-1 no     yes       -              17.06M
>>        opensolaris   yes    no        -              33.92M
>> This looks a bit confused to me.
>> Assume we use some tools like BFU to upgrade system,
>> BFU will change the existing mounted BE, not the new one.
>
> That's not necessarily a good thing is it?
>
>> So I thought the existing one "opensolaris" will be the upgraded
>> BE and "opensolaris-1" keeps the previous BE.
>
> With pkg image-udpate, its the opposite.  It clones the
> system, and operates on the clone.  You need to reboot to
> see the changes.

We have to activate the new BE before we reboot to it, right?
So if the new one can't boot, how to boot from the previous one?
boot up system by Live-CD and import the pool and repair it?

Thanks,
-Aubrey