Maintenance Activities for Boot Environments

Displaying the Status of All Boot Environments

Use the lustatus command to display the information about the boot environment. If no boot environment is specified, the status information for all boot environments on the system is displayed.

The following details for each boot environment are displayed:

• Name – Name of each boot environment.

• Complete – Indicates that no copy or create operations are in progress. Also, the boot environment can be booted. Any current activity or failure in a create or upgrade operation causes a boot environment to be incomplete. For example, if a copy operation is in process or scheduled for a boot environment, that boot environment is considered incomplete.

• Active – Indicates whether this is the active boot environment.

• ActiveOnReboot – Indicates whether the boot environment becomes active on next reboot of the system.

• CopyStatus – Indicates whether the creation or copy of the boot environment is scheduled, active, or in the process of being upgraded. A status of SCHEDULED prevents you from performing Live Upgrade copy, rename, or upgrade operations.

In this example, the status for all boot environments is displayed. To display the status of a specific boot environment, issue the command with the boot environment's name.

# su
# lustatus
boot environment   Is        Active  Active     Can        Copy
Name               Complete  Now     OnReboot   Delete     Status
------------------------------------------------------------------------
disk_a_S9           yes       yes     yes        no       -    
disk_b_S10database   yes       no      no         yes      COPYING  
disk_b_S9a          no        no      no         yes      - 

Based on the sample output, you could not perform copy, rename, or upgrade operations on disk_b_S9a because it is not complete, nor on disk_b_S10database because a Live Upgrade operation is in progress.

Updating a Previously Configured Boot Environment

You can update the contents of a previously configured boot environment with the Copy menu or the lumake command. File systems from the active (source) boot environment are copied to the target boot environment. The data on the target is also destroyed. A boot environment must have the status Complete before you can copy from it. See Displaying the Status of All Boot Environments for more information about how to determine a boot environment's status.

The copy job can be scheduled for a later time, and only one job can be scheduled at a time. To cancel a scheduled copy, see Canceling a Scheduled Create, Upgrade, or Copy Job.

The syntax for the lumake command is as follows:

# lumake -n  BE-name [-s source-BE] [-t  time] [-m email-address]

-n BE-name

Specifies the name of the boot environment that has file systems that are to be replaced.

-s source-BE

(Optional) Specifies the name of the source boot environment that contains the file systems to be copied to the target boot environment. If you omit this option, lumake uses the current boot environment as the source.

-t time

(Optional) Setsup a batch job to copy over file systems on a specified boot environment at a specified time. For information about how to format the time argument, see at(1) man page.

-m email-address

(Optional) Enables you to send an email of the lumake output to a specified address on command completion. email-address is not checked. You can use this option only in conjunction with -t.

Example 7-1 Updating a Previously Configured Boot Environment

In this example, file systems from first_disk are copied to second_disk. When the job is completed, an email is sent to Joe at anywhere.com.

# su
# lumake -n  second_disk -s first_disk -m joe@anywhere.com

The files on first_disk are copied to second_disk and email is sent for notification. To find how to cancel a scheduled copy, see Canceling a Scheduled Create, Upgrade, or Copy Job.

Canceling a Scheduled Create, Upgrade, or Copy Job

A boot environment's scheduled creation, upgrade, or copy job can be canceled just prior to the time the job starts. The job can be scheduled by the lumake command. At any time, only one job can be scheduled on a system.

To cancel a scheduled job, become superuser or assume an equivalent role and issue the lucancel command.

Comparing Boot Environments

Use the lucompare command to check for differences between the active boot environment and other boot environments. To make a comparison, the inactive boot environment must be in a Complete state and cannot have a copy job that is pending. See Displaying the Status of All Boot Environments.

The lucompare command generates a comparison of boot environments that includes the contents of any non-global zones.

The specified boot environment cannot have any partitions that are mounted with lumount or mount.

The syntax for the lucompare command is as follows:

# /usr/sbin/lucompare -i  infile (or) -t -o  outfile BE-name

-i  infile

Compare files that are listed in infile. The files to be compared should have absolute file names. If the entry in the file is a directory, then comparison is recursive to the directory. Use either this option or -t, not both.

-t

Compare only nonbinary files. This comparison uses the file(1) command on each file to determine whether the file is a text file. Use either this option or -i, not both.

-o  outfile

Redirect the output of differences to outfile.

BE-name

Specifies the name of the boot environment that is compared to the active boot environment.

Example 7-2 Comparing Boot Environments

In this example, first_disk boot environment (source) is compared to second_disk boot environment and the results are sent to a file.

# /usr/sbin/lucompare -i  /etc/lu/compare/ \
-o /var/tmp/compare.out second_disk

Deleting an Inactive Boot Environment

Use the ludelete command to remove a boot environment. Note the following limitations.

• You cannot delete the active boot environment or the boot environment that is activated on the next reboot.

• The boot environment to be deleted must be complete. A complete boot environment is not participating in an operation that will change its status. Displaying the Status of All Boot Environments describes how to determine a boot environment's status.

• You cannot delete a boot environment that has file systems mounted with lumount.

• x86 only: Starting with the Solaris 10 1/06 release, you cannot delete a boot environment that contains the active GRUB menu. Use the lumake or luupgrade commands to reuse the boot environment. To determine which boot environment contains the active GRUB menu, see Chapter 13, Managing the Oracle Solaris Boot Archives (Tasks), in Oracle Solaris Administration: Basic Administration.

The syntax for the ludelete command is as follows:

# ludelete BE-name

BE-name

Specifies the name of the inactive boot environment that is to be deleted

Example 7-3 Deleting an Inactive Boot Environment

In this example, the boot environment second_disk is deleted.

# ludelete second_disk

Displaying the Name of the Active Boot Environment

Use the lucurr command to display the name of the currently running boot environment. If no boot environments are configured on the system, the message “No Boot Environments are defined” is displayed. Note that lucurr reports only the name of the current boot environment, not the boot environment that is active on the next reboot. See Displaying the Status of All Boot Environments to determine a boot environment's status.

Example 7-4 Displaying the Name of the Active Boot Environment

In this example, the name of the current boot environment is displayed.

# /usr/sbin/lucurr
solaris10