OpenSolaris Managing Boot Environments
Previous Next

Destroying a Boot Environment

If you want to make more room available on your system, you can use the beadm command to destroy an existing boot environment.

Note the following specifications:

  • You cannot destroy the boot environment that is currently booted.

  • The beadm destroy command automatically removes the destroyed boot environment's entry from the x86 GRUB menu or the SPARC boot menu.

  • The beadm destroy command destroys only the critical or nonshared datasets of the boot environment. Shared datasets are located outside of the boot environment root dataset area and are not affected when a boot environment is destroyed.

    See the following example, where BE1 and BE2 share the rpool/export and rpool/export/home datasets. The datasets include the following:

    rpool/ROOT/BE1
    rpool/ROOT/BE1/opt
    rpool/ROOT/BE2
    rpool/ROOT/BE2/opt
    rpool/export
    rpool/export/home

    Destroy BE2 by using the following command:

    beadm destroy BE2

    The shared datasets, rpool/export and rpool/export/home, are not destroyed when the boot environment BE2 is destroyed. The following datasets remain.

    rpool/ROOT/BE1
    rpool/ROOT/BE1/opt
    rpool/export
    rpool/export/home

How to Destroy an Existing Boot Environment

  • To destroy a boot environment, type the following:
    $ beadm destroy beName

    Note - The beadm destroy command asks for confirmation before destroying the boot environment. Add the -F option to the beadm destroy command to force destruction of the boot environment without a confirmation request. Add the -f option to force destruction of the boot environment even if its mounted.


Previous Next