Creating a New Boot Environment

Creating a boot environment provides a method of copying critical file systems from the active boot environment to a new boot environment. The lucreate command enables reorganizing a disk if necessary, customizing file systems, and copying the critical file systems to the new boot environment.

Before file systems are copied to the new boot environment, they can be customized so that critical file system directories are either merged into their parent directory or split from their parent directory. User-defined (shareable) file systems are shared between boot environments by default. But shareable file systems can be copied if needed. Swap, which is a shareable volume, can be split and merged also. For an overview of critical and shareable file systems, see File System Types.

The lucreate command that is used with the -m option specifies which file systems and the number of file systems to be created in the new boot environment. You must specify the exact number of file systems you want to create by repeating this option. For example, a single use of the -m option specifies where to put all the file systems. You merge all the file systems from the original boot environment into the one file system that is specified by the -m option. If you specify the -m option twice, you create two file systems. When using the -m option to create file systems, follow these guidelines:

• You must specify one -m option for the root (/) file system for the new boot environment. If you run lucreate without the -m option, the Configuration menu is displayed. The Configuration menu enables you to customize the new boot environment by redirecting files onto new mount points.

• Any critical file systems that exist in the current boot environment and are not specified in a -m option are merged into the next highest level file system created.

• Only the file systems that are specified by the -m option are created on the new boot environment. If your current boot environment contains multiple file systems and you want to have the same number of file systems in the new boot environment created, you must specify one -m option for each file system to be created. For example, if you have file systems for root (/), /opt, and /var, you would use one -m option for each file system on the new boot environment.

• Do not duplicate a mount point. For example, you cannot have two root (/) file systems.

How to Create a Boot Environment for the First Time

• To create the new boot environment, type:

  # lucreate [-A 'BE-description'] -c BE-name \
   -m mountpoint:device[,metadevice]:fs-options [-m ...] -n BE-name

  -A 'BE-description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE-name). The description can be any length and can contain any characters.

  -c BE-name

  Assigns the name BE-name to the active boot environment. This option is not required and is only used when the first boot environment is created. If you run lucreate for the first time and you omit the -c option, the software creates a default name for you.

  The default name is chosen according to the following criteria:

  • If the physical boot device can be determined, then the base name of the physical boot device is used to name the current boot environment.

    For example, if the physical boot device is /dev/dsk/c0t0d0s0, then the current boot environment is given the name c0t0d0s0.

  • If the physical boot device cannot be determined, then names from the uname command with the -s and -r options are combined to produce the name.

    For example, if uname -s returns the OS name of SunOS and uname -r returns the release name of 5.9, then the name SunOS5.9 is given to the current boot environment.

  • If neither of these commands can determine the name, then the name current is used to name the current boot environment.

  ---

  Note - If you use the -c option after the first boot environment creation, the option is ignored or an error message is displayed.

  • If the name specified is the same as the current boot environment name, the option is ignored.

  • If the name specified is different than the current boot environment name, then an error message is displayed and the creation fails. The following example shows a boot environment name that causes an error message.

    # lucurr 
    c0t0d0s0
    # lucreate -c /dev/dsk/c1t1d1s1 -n newbe -m /:/dev/dsk/c1t1d1s1:ufs
    ERROR: current boot environment name is c0t0d0s0: cannot change
    name using <-c c1t1d1s1>

  ---

  -m mountpoint:device[,metadevice]:fs-options [-m ...]

  Specifies the file system configuration of the new boot environment in the vfstab file. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager volume, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/md/vxfs/dsk/dnum

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs-options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE-name

  The name of the boot environment to be created. BE-name must be unique on the system.

  When creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-1 Creating a Boot Environment

In this example, the active boot environment is named first_disk. The mount points for the file systems are noted by using the -m option. Two file systems are created, root (/) and /usr. The new boot environment is named second_disk. A description, mydescription, is associated with the name second_disk. Swap, in the new boot environment second_disk, is automatically shared from the source, first_disk.

# lucreate -A 'mydescription' -c first_disk  -m /:/dev/dsk/c0t4d0s0:ufs \
-m /usr:/dev/dsk/c0t4d0s3:ufs  -n second_disk

How to Create a Boot Environment and Merge File Systems

• Type:

  # lucreate  -A 'BE_description' \ 
  -m mountpoint:device[,metadevice]:fs_options \ 
  -m [...] -m mountpoint:merged:fs_options -n BE_name

  -A BE_description

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique on the system.

  When creation of the new boot environment is complete, it can be upgraded and activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-2 Creating a Boot Environment and Merging File Systems

In this example, the file systems on the current boot environment are root (/), /usr, and /opt. The /opt file system is combined with its parent file system /usr. The new boot environment is named second_disk. A description, mydescription, is associated with the name second_disk.

# lucreate -A 'mydescription' -c first_disk \
 -m /:/dev/dsk/c0t4d0s0:ufs -m /usr:/dev/dsk/c0t4d0s1:ufs \
 -m /usr/opt:merged:ufs -n second_disk

How to Create a Boot Environment and Split File Systems

When splitting a directory into multiple mount points, hard links are not maintained across file systems. For example, if /usr/stuff1/file is hard linked to /usr/stuff2/file, and /usr/stuff1 and /usr/stuff2 are split into separate file systems, the link between the files no longer exists. lucreate issues a warning message and a symbolic link is created to replace the lost hard link.

• Type:

  # lucreate [-A 'BE_description'] \
   -m mountpoint:device[,metadevice]:fs_options \ 
  -m mountpoint:device[,metadevice]:fs_options -n new_BE

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and contain any characters.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique on the system.

Example 4-3 Creating a Boot Environment and Splitting File Systems

In this example, the preceding command splits the root (/) file system over multiple disk slices in the new boot environment. Assume a source boot environment that has /usr, /var, and /opt on root (/): /dev/dsk/c0t0d0s0 /.

On the new boot environment, separate /usr, /var, and /opt, mounting these file systems on their own slices, as follows:

/dev/dsk/c0t1d0s0 /

/dev/dsk/c0t1d0s1 /var

/dev/dsk/c0t1d0s7 /usr

/dev/dsk/c0t1d0s5 /opt

A description, mydescription, is associated with the boot environment name second_disk.

# lucreate -A 'mydescription' -c first_disk \
 -m /:/dev/dsk/c0t1d0s0:ufs -m /usr:/dev/dsk/c0t1d0s7:ufs  \ 
-m /var:/dev/dsk/c0t1d0s1:ufs -m /opt:/dev/dsk/c0t1d0s5:ufs \ 
-n second_disk

Next Steps

When creation of the new boot environment is complete, it can be upgraded and activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

How to Create a Boot Environment and Reconfiguring Swap

Swap slices are shared between boot environments by default. By not specifying swap with the -m option, your current and new boot environment share the same swap slices. If you want to reconfigure the new boot environment's swap, use the -m option to add or remove swap slices in the new boot environment.

• Type:

  # lucreate  [-A 'BE_description'] \
   -m mountpoint:device[,metadevice]:fs_options \ 
  -m -:device:swap -n BE_name

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique.

  The new boot environment is created with swap moved to a different slice or device.

  When creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-4 Creating a Boot Environment and Reconfiguring Swap

In this example, the current boot environment contains root (/) on /dev/dsk/c0t0d0s0 and swap is on /dev/dsk/c0t0d0s1. The new boot environment copies root (/) to /dev/dsk/c0t4d0s0 and uses both /dev/dsk/c0t0d0s1 and /dev/dsk/c0t4d0s1 as swap slices. A description, mydescription, is associated with the boot environment name second_disk.

# lucreate -A 'mydescription' -c first_disk \ 
-m /:/dev/dsk/c0t4d0s0:ufs -m -:/dev/dsk/c0t0d0s1:swap \ 
-m -:/dev/dsk/c0t4d0s1:swap -n second_disk 

These swap assignments are effective only after booting from second_disk. If you have a long list of swap slices, use the -M option. See How to Create a Boot Environment and Reconfigure Swap by Using a List.

How to Create a Boot Environment and Reconfigure Swap by Using a List

If you have a long list of swap slices, create a swap list. lucreate uses this list for the swap slices in the new boot environment.

1. Create a list of swap slices to be used in the new boot environment.

   The location and name of this file is user defined. In this example, the content of the /etc/lu/swapslices file is a list of devices and slices:

   -:/dev/dsk/c0t3d0s2:swap
   -:/dev/dsk/c0t3d0s2:swap
   -:/dev/dsk/c0t4d0s2:swap
   -:/dev/dsk/c0t5d0s2:swap
   -:/dev/dsk/c1t3d0s2:swap
   -:/dev/dsk/c1t4d0s2:swap
   -:/dev/dsk/c1t5d0s2:swap

2. Type:

   # lucreate  [-A 'BE_description'] \
    -m mountpoint:device[,metadevice]:fs_options \
   -M slice_list  -n BE_name

   -A 'BE_description'

   (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

   -m mountpoint:device[,metadevice]:fs_options [-m...]

   Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

   • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

   • device field can be one of the following:

     • The name of a disk device, of the form /dev/dsk/cwtxdysz

     • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

     • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

     • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

   • fs_options field can be one of the following:

     • ufs, which indicates a UFS file system.

     • vxfs, which indicates a Veritas file system.

     • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

     • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

   -M slice_list

   List of -m options, which are collected in the file slice_list. Specify these arguments in the format that is specified for -m. Comment lines, which begin with a hash mark (#), are ignored. The -M option is useful when you have a long list of file systems for a boot environment. Note that you can combine -m and -M options. For example, you can store swap slices in slice_list and specify root (/) and /usr slices with -m.

   The -m and -M options support the listing of multiple slices for a particular mount point. In processing these slices, lucreate skips any unavailable slices and selects the first available slice.

   -n BE_name

   The name of the boot environment to be created. BE_name must be unique.

   When creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-5 Create a Boot Environment and Reconfiguring Swap By Using a List

In this example, swap in the new boot environment is the list of slices that are noted in the /etc/lu/swapslices file. A description, mydescription, is associated with the name second_disk.

# lucreate -A 'mydescription' -c first_disk \ 
-m /:/dev/dsk/c02t4d0s0:ufs -m /usr:/dev/dsk/c02t4d0s1:ufs \ 
-M /etc/lu/swapslices -n second_disk 

How to Create a Boot Environment and Copy a Shareable File System

If you want a shareable file system to be copied to the new boot environment, specify the mount point to be copied with the -m option. Otherwise, shareable file systems are shared by default, and maintain the same mount point in the vfstab file. Any updating that is applied to the shareable file system is available to both boot environments.

• Create the boot environment.

  # lucreate [-A 'BE_description'] \ 
  -m mountpoint:device[,metadevice]:fs_options \ 
  -m mountpoint:device[,metadevice]:fs_options  -n BE_name

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique.

  When creation of the new boot environment is complete, it can be upgraded and activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-6 Creating a Boot Environment and Copying a Shareable File System

In this example, the current boot environment contains two file systems, root (/) and /home. In the new boot environment, the root (/) file system is split into two file systems, root (/) and /usr. The /home file system is copied to the new boot environment. A description, mydescription, is associated with the boot environment name second_disk.

# lucreate -A 'mydescription' -c first_disk \ 
-m /:/dev/dsk/c0t4d0s0:ufs -m /usr:/dev/dsk/c0t4d0s3:ufs \
-m /home:/dev/dsk/c0t4d0s4:ufs -n second_disk

How to Create a Boot Environment From a Different Source

The lucreate command creates a boot environment that is based on the file systems in the active boot environment. If you want to create a boot environment based on a boot environment other than the active boot environment, use lucreate with the -s option.

• Create the boot environment.

  # lucreate [-A 'BE_description'] -s source_BE_name 
  -m mountpoint:device[,metadevice]:fs_options -n BE_name

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

  -s source_BE_name

  Specifies the source boot environment for the new boot environment. The source would not be the active boot environment.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique on the system.

  When creation of the new boot environment is complete, it can be upgraded and activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-7 Creating a Boot Environment From a Different Source

In this example, a boot environment is created that is based on the root (/) file system in the source boot environment named third_disk. third_disk is not the active boot environment. A description, mydescription, is associated with the new boot environment named second_disk.

# lucreate -A 'mydescription' -s third_disk \ 
-m /:/dev/dsk/c0t4d0s0:ufs  -n second_disk

How to Create an Empty Boot Environment for a Flash Archive

The lucreate command creates a boot environment that is based on the file systems in the active boot environment. When using the lucreate command with the -s - option, lucreate quickly creates an empty boot environment. The slices are reserved for the file systems that are specified, but no file systems are copied. The boot environment is named, but not actually created until installed with a Flash Archive. When the empty boot environment is installed with an archive, file systems are installed on the reserved slices.

• Create the empty boot environment.

  # lucreate -A 'BE_name' -s - \ 
  -m mountpoint:device[,metadevice]:fs_options -n BE_name

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name (BE_name). The description can be any length and can contain any characters.

  -s -

  Specifies that an empty boot environment be created.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager metadevice, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/vx/dsk/volume_name

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options field can be one of the following:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device. For a description of these keywords, see How to Create a Boot Environment With RAID-1 Volumes (Mirrors).

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique on the system.

Example 4-8 Creating an Empty Boot Environment for a Flash Archive

In this example, a boot environment is created but contains no file systems. A description, mydescription, is associated with the new boot environment that is named second_disk.

# lucreate -A 'mydescription' -s - \ 
-m /:/dev/dsk/c0t1d0s0:ufs  -n second_disk

When creation of the empty boot environment is complete, a Flash archive can be installed and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

For an example of creating and populating an empty boot environment, see Example of Creating an Empty Boot Environment and Installing a Flash Archive .

How to Create a Boot Environment With RAID-1 Volumes (Mirrors)

When you create a boot environment, Live Upgrade uses Solaris Volume Manager technology to create RAID-1 volumes. When creating a boot environment, you can use Live Upgrade to manage the following tasks.

• Remove a single-slice concatenation (submirror) from a RAID-1 volume (mirror). The contents can be saved to become the content of the new boot environment if necessary. Because the contents are not copied, the new boot environment can be quickly created. After the submirror is detached from a mirror, it is no longer part of the original mirror. Reads and writes to the submirror are no longer performed through the mirror.

• Create a boot environment that contains a mirror.

• Attach a single-slice concatenation to the newly created mirror.

Before You Begin

To use the mirroring capabilities of Live Upgrade, you must create a state database and a state database replica. A state database stores information about disk about the state of your Solaris Volume Manager configuration.

• For information about creating a state database, see Chapter 6, State Database (Overview), in Solaris Volume Manager Administration Guide.

• For an overview of Solaris Volume Manager and the tasks that Live Upgrade can provide, see Creating a Boot Environment With RAID-1 Volume File Systems.

• For in-depth information about complex Solaris Volume Manager configurations that are not allowed when using Live Upgrade, see Chapter 2, Storage Management Concepts, in Solaris Volume Manager Administration Guide.

• To create the new boot environment, type:

  # lucreate [-A 'BE_description']  \ 
  -m mountpoint:device[,metadevice]:fs_options [-m...] \ 
  -n BE_name

  -A 'BE_description'

  (Optional) Enables the creation of a boot environment description that is associated with the boot environment name BE_name. The description can be any length and can contain any characters.

  -m mountpoint:device[,metadevice]:fs_options [-m...]

  Specifies the file systems' configuration of the new boot environment in the vfstab. The file systems that are specified as arguments to -m can be on the same disk or they can be spread across multiple disks. Use this option as many times as needed to create the number of file systems that are needed.

  • mountpoint can be any valid mount point or – (hyphen), indicating a swap partition.

  • device field can be one of the following:

    • The name of a disk device, of the form /dev/dsk/cwtxdysz

    • The name of a Solaris Volume Manager volume, of the form /dev/md/dsk/dnum

    • The name of a Veritas Volume Manager volume, of the form /dev/md/vxfs/dsk/dnum

    • The keyword merged, indicating that the file system at the specified mount point is to be merged with its parent

  • fs_options can be one of the following types of file systems and keywords:

    • ufs, which indicates a UFS file system.

    • vxfs, which indicates a Veritas file system.

    • swap, which indicates a swap volume. The swap mount point must be a – (hyphen).

    • For file systems that are logical devices (mirrors), several keywords specify actions to be applied to the file systems. These keywords can create a logical device, change the configuration of a logical device, or delete a logical device.

      • mirror creates a RAID–1 volume or mirror on the specified device. In subsequent -m options, you must specify attach to attach at least one concatenation to the new mirror. The specified device must be correctly named. For example, a logical device name of /dev/md/dsk/d10 can serve as a mirror name. For more information about naming devices, see Overview of Solaris Volume Manager Components in Solaris Volume Manager Administration Guide.

      • detach removes a concatenation from a volume that is associated with a specified mount point. The volume does not need to be specified.

      • attach attaches a concatenation to the mirror that is associated with a specified mount point. The physical disk slice that is specified is made into a single device concatenation for attaching to the mirror. To specify a concatenation to attach to a disk, you append a comma and the name of that concatenation to the device name. If you omit the comma and the concatenation name, lucreate selects a free volume for the concatenation.

        lucreate allows you to create only concatenations that contain a single physical slice. This command allows you to attach up to three concatenations to a mirror.

      • preserve saves the existing file system and its content. This keyword enables you to bypass the copying process that copies the content of the source boot environment. Saving the content enables a quick creation of the new boot environment. For a particular mount point, you can use preserve with only one physical device. When you use preserve, lucreate checks that the device's content is suitable for a specified file system. This check is limited and cannot guarantee suitability.

        The preserve keyword can be used with both a physical slice and a Solaris Volume Manager volume.

        • If you use the preserve keyword when the UFS file system is on a physical slice, the content of the UFS file system is saved on the slice. In the following example of the -m option, the preserve keyword saves the content of the physical device c0t0d0s0 as the file system for the mount point for the root (/) file system.

          -m /:/dev/dsk/c0t0d0s0:preserve,ufs

        • If you use the preserve keyword when the UFS file system is on a volume, the contents of the UFS file system are saved on the volume.

          In the following example of the -m option, the preserve keyword saves the contents of the RAID-1 volume (mirror) d10 as the file system for the mount point for the root (/) file system.

          -m /:/dev/md/dsk/d10:preserve,ufs

          In the following example of the -m option, a RAID-1 volume (mirror) d10 is configured as the file system for the mount point for the root (/) file system. The single-slice concatenation d20 is detached from its current mirror. d20 is attached to mirror d10. The root (/) file system is preserved on submirror d20.

          -m /:/dev/md/dsk/d10:mirror,ufs -m /:/dev/md/dsk/d20:detach,attach,preserve

  -n BE_name

  The name of the boot environment to be created. BE_name must be unique on the system.

  When the creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-9 Creating a Boot Environment With a Mirror and Specifying Devices

In this example, the mount points for the file systems are specified by using the -m option.

• A description, mydescription, is associated with the name another_disk.

• lucreate configures a UFS file system for the mount point root (/). A mirror, d10, is created. This mirror is the receptacle for the current boot environment's root (/) file system that is copied to the mirror d10. All data on the mirror d10 is overwritten.

• Two slices, c0t0d0s0 and c0t1d0s0, are submirrors, d1 and d2. These two submirrors are added to mirror d10.

• The new boot environment is named another_disk.

# lucreate -A 'mydescription' \ 
-m /:/dev/md/dsk/d10:ufs,mirror \ 
-m /:/dev/dsk/c0t0d0s0,/dev/md/dsk/d1:attach \ 
-m /:/dev/dsk/c0t1c0s0,/dev/md/dsk/d2:attach -n another_disk

Example 4-10 Creating a Boot Environment With a Mirror and Not Specifying a Submirror Name

In this example, the mount points for the file systems are specified by using the -m option.

• A description, mydescription, is associated with the name another_disk.

• lucreate configures a UFS file system for the mount point root (/). A mirror, d10, is created. This mirror is the receptacle for the current boot environment's root (/) file system that is copied to the mirror d10. All data on the mirror d10 is overwritten.

• Two slices, c0t0d0s0 and c0t1d0s0, are specified to be used as submirrors. The submirrors are not specified, but the lucreate command chooses names from a list of available volume names. These two submirrors are attached to mirror d10.

• The new boot environment is named another_disk.

# lucreate -A 'mydescription' \ 
-m /:/dev/md/dsk/d10:ufs,mirror \ 
-m /:/dev/dsk/c0t0d0s0:attach \ 
-m /:/dev/dsk/c0t1d0s0:attach -n another_disk

When the creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-11 Creating a Boot Environment and Detaching a Submirror

In this example, the mount points for the file systems are specified by using the -m option.

• A description, mydescription, is associated with the name another_disk.

• lucreate configures a UFS file system for the mount point root (/). A mirror, d10, is created.

• Slice c0t0d0s0 is removed from its current mirror. The slice is specified to be submirror d1 and is added to mirror d10. The contents of the submirror, the root (/) file system, are saved and no copy occurs. Slice c0t1d0s0 is submirror d2 and is added to mirror d10.

• The new boot environment is named another_disk.

# lucreate -A 'mydescription' \ 
-m /:/dev/md/dsk/d10:ufs,mirror \ 
-m /:/dev/dsk/c0t0d0s0,/dev/md/dsk/d1:detach,attach,preserve \ 
-m /:/dev/dsk/c0t1d0s0,/dev/md/dsk/d2:attach -n another_disk

When the creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-12 Creating a Boot Environment, Detaching a Submirror, and Saving Its Contents

In this example, the mount points for the file systems are specified by using the -m option.

• A description, mydescription, is associated with the name another_disk.

• lucreate configures a UFS file system for the mount point root (/). A mirror, d20, is created.

• Slice c0t0d0s0 is removed from its current mirror and added to the mirror d20. The name of the submirror is not specified. The contents of the submirror, the root (/) file system, are saved and no copy occurs.

• The new boot environment is named another_disk.

# lucreate -A 'mydescription' \ 
-m /:/dev/md/dsk/d20:ufs,mirror \ 
-m /:/dev/dsk/c0t0d0s0:detach,attach,preserve \ 
-n another_disk

When the creation of the new boot environment is complete, the boot environment can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Example 4-13 Creating a Boot Environment With Two Mirrors

In this example, the mount points for the file systems are specified by using the -m option.

• A description, mydescription, is associated with the name another_disk.

• lucreate configures a UFS file system for the mount point root (/). A mirror, d10, is created. This mirror is the receptacle for the current boot environment's root (/) file system that is copied to the mirror d10. All data on the mirror d10 is overwritten.

• Two slices, c0t0d0s0 and c0t1d0s0, are submirrors d1 and d2. These two submirrors are added to mirror d10.

• lucreate configures UFS file system for the mount point /opt. A mirror, d11, is created. This mirror is the receptacle for the current boot environment's /opt file system that is copied to the mirror d11. All data on the mirror d11 is overwritten.

• Two slices, c2t0d0s1 and c3t1d0s1, are submirrors d3 and d4. These two submirrors are added to mirror d11.

• The new boot environment is named another_disk.

# lucreate -A 'mydescription' \ 
-m /:/dev/md/dsk/d10:ufs,mirror \ 
-m /:/dev/dsk/c0t0d0s0,/dev/md/dsk/d1:attach \ 
-m /:/dev/dsk/c0t1d0s0,/dev/md/dsk/d2:attach \ 
-m /opt:/dev/md/dsk/d11:ufs,mirror \ 
-m /opt:/dev/dsk/c2t0d0s1,/dev/md/dsk/d3:attach \ 
-m /opt:/dev/dsk/c3t1d0s1,/dev/md/dsk/d4:attach -n another_disk

When the creation of the new boot environment is complete, it can be upgraded and can be activated (made bootable). See Chapter 5, Upgrading With Live Upgrade (Tasks).

Creating a Boot Environment and Customizing the Content

The content of the file system on the new boot environment can be modified by using the inclusion and exclusion options. Directories and files are not copied to the new boot environment.

The inclusion and exclusion options appear in the lucreate command syntax as follows:

# lucreate -m mountpoint:device[,metadevice]:fs_options [-m ...]  \ 
[-x exclude-dir] [-y include] \
[-Y include-list-file] \
[-f exclude-list-file]\  
[-z filter-list] [-I] -n BE_name

-x exclude-dir

Excludes files and directories by not copying them to the new boot environment. You can use multiple instances of this option to exclude more than one file or directory.

exclude-dir is the name of the directory or file.

-y include-dir

Copies directories and files that are listed to the new boot environment. This option is used when you have excluded a directory but want to restore individual subdirectories or files.

include-dir is the name of the subdirectory or file to be included.

-Y list-filename

Copies directories and files from a list to the new boot environment. This option is used when you have excluded a directory but want to restore individual subdirectories or files.

• list-filename is the full path to a file that contains a list.

• The list-filename file must contain one file per line.

• If a line item is a directory, all subdirectories and files beneath that directory are included. If a line item is a file, only that file is included.

-f list-filename

Uses a list to exclude directories and files by not copying them to the new boot environment.

• list-filename is the full path to a file that contains a list.

• The list-filename file must contain one file per line.

-z list-filename

Uses a list to copy directories and files to the new boot environment. Each file or directory in the list is noted with a plus “+” or minus “-”. A plus indicates an included file or directory and the minus indicates an excluded file or directory.

• list-filename is the full path to a file that contains a list.

• The list-filename file must contain one file per line. A space must follow the plus or minus before the file name.

• If a line item is a directory and is indicated with a + (plus), all subdirectories and files beneath that directory are included. If a line item is a file and is indicated with a + (plus), only that file is included.

-I

Overrides the integrity check of system files. Use this option with caution.

To prevent you from removing important system files from a boot environment, lucreate runs an integrity check. This check examines all files that are registered in the system package database and stops the boot environment creation if any files are excluded. Use of this option overrides this integrity check. This option creates the boot environment more quickly, but might not detect problems.