Project

General

Profile

Bug #2888

beadm should create new ZBE-x for zones on activate state

Added by Igor Kozhukhov almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2012-06-16
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

we have use case:
1. beadm create <newBE>
2. beadm destroy <newBE>

new zbe-x for zones have been created in (1) state and not removed.

example:

# zfs list
-----
rpool/zones                1.29G  3.56G    33K  /zones
rpool/zones/t1              736M  3.56G    33K  /zones/t1
rpool/zones/t1/ROOT         736M  3.56G    31K  legacy
rpool/zones/t1/ROOT/zbe      35K  3.56G   736M  legacy
rpool/zones/t1/ROOT/zbe-1   736M  3.56G   736M  legacy
rpool/zones/t2              584M  3.56G    33K  /zones/t2
rpool/zones/t2/ROOT         584M  3.56G    31K  legacy
rpool/zones/t2/ROOT/zbe      35K  3.56G   584M  legacy
rpool/zones/t2/ROOT/zbe-1   584M  3.56G   584M  legacy
-----

# beadm create newbe
# zfs list
-----
rpool/zones                1.29G  3.56G    33K  /zones
rpool/zones/t1              736M  3.56G    33K  /zones/t1
rpool/zones/t1/ROOT         736M  3.56G    31K  legacy
rpool/zones/t1/ROOT/zbe      35K  3.56G   736M  legacy
rpool/zones/t1/ROOT/zbe-1   736M  3.56G   736M  legacy
rpool/zones/t1/ROOT/zbe-2  49.5K  3.56G   736M  legacy
rpool/zones/t2              584M  3.56G    33K  /zones/t2
rpool/zones/t2/ROOT         584M  3.56G    31K  legacy
rpool/zones/t2/ROOT/zbe      35K  3.56G   584M  legacy
rpool/zones/t2/ROOT/zbe-1   584M  3.56G   584M  legacy
rpool/zones/t2/ROOT/zbe-2  55.5K  3.56G   584M  legacy
-----

# beadm destroy newbe
# zfs list
-----
rpool/zones                1.29G  3.56G    33K  /zones
rpool/zones/t1              736M  3.56G    33K  /zones/t1
rpool/zones/t1/ROOT         736M  3.56G    31K  legacy
rpool/zones/t1/ROOT/zbe      35K  3.56G   736M  legacy
rpool/zones/t1/ROOT/zbe-1   736M  3.56G   736M  legacy
rpool/zones/t1/ROOT/zbe-2  49.5K  3.56G   736M  legacy
rpool/zones/t2              584M  3.56G    33K  /zones/t2
rpool/zones/t2/ROOT         584M  3.56G    31K  legacy
rpool/zones/t2/ROOT/zbe      35K  3.56G   584M  legacy
rpool/zones/t2/ROOT/zbe-1   584M  3.56G   584M  legacy
rpool/zones/t2/ROOT/zbe-2  55.5K  3.56G   584M  legacy
-----

as we can see - new zbe-2 have not beed destroyed

I think - it is logic issue of BEADM.
we have to create new zbe-x for zones when we use 'beadm activate newbe'

History

#1

Updated by Rich Lowe almost 8 years ago

boot environments should be created under 'beadm create' not 'beadm activate'.

I don't understand how the failure to destroy a ZBE on 'beadm destroy' leads you to think we should create extra ones on 'beadm activate'.

Also available in: Atom PDF