Project

General

Profile

Bug #4410

beadm unsupported to destroy ZBE-x in zone

Added by Igor Kozhukhov almost 6 years ago. Updated over 5 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2013-12-20
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

# beadm list
BE     Active Mountpoint Space Policy Created
zbe    xb     -          37.0K static 2013-05-27 15:39
zbe-1  xb     -          27.0K static 2013-06-29 02:44
zbe-10 xb     -          39.0K static 2013-12-03 10:12
zbe-11 NR     /          13.5G static 2013-12-14 14:02
zbe-2  xb     -          32.0K static 2013-07-20 21:01
zbe-3  xb     -          36.0K static 2013-09-16 03:21
zbe-4  xb     -          29.0K static 2013-09-21 17:47
zbe-5  xb     -          26.0K static 2013-10-22 17:57
zbe-6  xb     -          595K  static 2013-11-03 23:31
zbe-7  xb     -          746K  static 2013-11-06 14:04
zbe-8  xb     -          31.0K static 2013-11-19 03:22
zbe-9  xb     -          79.5K static 2013-11-22 04:58
# beadm destroy zbe-1
Are you sure you want to destroy zbe-1?
This action cannot be undone (y/[n]): y
Unable to destroy zbe-1.
Operation not supported.

History

#1

Updated by Rich Lowe over 5 years ago

  • Status changed from New to Feedback

You can't destroy a zone BE that is required by another global BE, that would be (logically) affecting the state of the global BE from within the zone. See the documentation of the 'x' flag in Active. It indicates that the ZBE belongs to a global BE other than the one currently booted, and that it cannot be deleted.

#2

Updated by Igor Kozhukhov over 5 years ago

Rich Lowe wrote:

You can't destroy a zone BE that is required by another global BE, that would be (logically) affecting the state of the global BE from within the zone. See the documentation of the 'x' flag in Active. It indicates that the ZBE belongs to a global BE other than the one currently booted, and that it cannot be deleted.

Could you please describe dependencies to global BE from zone BE ?
as i know we are using UID from global BE in zone BE for identification boot BE for zone.
we are changing UID global BE in zone BE if we have activated another global BE.
I have no found dependencies of global BE from zone BE.

For my opinion we should to use create/destroy/activate operation in zone with zone BE.

#3

Updated by Rich Lowe over 5 years ago

If the global zone administrator boots an older BE, the zone will not function, because you deleted the BE that matches it. There will exist a zone with no root dataset.

This is exactly the same as the requirements in the global zone, you cannot delete an active boot environment -- the zone BEs just happen to be "active" in other global BEs.

You can use create/destroy/activate in zones, but only with valid zone environments which are not active (at all).

Also available in: Atom PDF