When migrated to different hosts, native non-global zones can accumulatezone boot environments that are not associated with an existing global zone. Anon-global zone boot environment is known as an orphaned bootenvironment.
If a zone boot environment that is not associated with any global zone isselected, it is cloned. This cloned boot environment will be updated andre-parented to the active global boot environment. The orphaned boot environmentwill continue to exist.
This section provides the following information to manage zone bootenvironments duringzoneadm attach operations of azone:
The optionsattach-last-booted-zbe anddestroy-orphan-zbes can be used with theforce-zbe-clone ordeny-zbe-cloneoptions.
This option destroys all zone boot environments that are not associatedwith any global zone.
To destroy all orphan zone boot environments duringattach, use:
-x destroy-orphan-zbes
If the selected zone boot environment is associated with the currentlyactive global zone boot environment, the selected zone boot environment isattached. This behavior can be changed by using–xforce-zbe-clone.
To select a different global zone boot environment, use:
-x force-zbe-clone
By default, if either of the following are true, the selected zone bootenvironment is cloned and the clone is attached.
The selected zone boot environment is associated with another global zoneboot environment.
The selected zone boot environment is an orphaned boot environment that isnot associated with any global zone boot environment.
An attach operation that usesdeny-zbe-clone fails whenyou try to attach an orphaned zone boot environment that is marked active onreboot. The zone boot environment must be marked inactive to use thisoption.
The original zone boot environment continues to exist.
To deny clone and attach, use:
-x deny-zbe-clone
Orphaned boot environments are indicated bybeadm usingtheO flag in theactive column. In thefollowing output,solaris-0,solaris-1,andsolaris-2 are orphaned.
root@t1: # beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- solaris-0 !RO - 3.40M static 2014-01-17 15:04 solaris-1 !RO - 3.85M static 2014-02-09 18:11 solaris-2 !RO - 39.0K static 2014-02-10 04:54 solaris-3 !R - 2.19G static 2014-02-12 16:56 solaris-5 NR / 2.43G static 2014-03-20 04:38
Boot environments that are shown as orphaned can be destroyed withbeadm destroy. To destroy all orphaned boot environments, usethe–O withbeadm destroy.
For more information on boot environments, seeCreating and Administering Oracle Solaris 11.3 Boot Environments and thebeadm(1M) man page.