Managing ZFS Root Pool Components (Overview)

ZFS is the default root file system in the Oracle Solaris 11 release. Review the following considerations when installing the Oracle Solaris release.

• Installation – In the Oracle Solaris 11 release, you can install and boot from a ZFS root file system in the following ways:

  • Live CD (x86 only) – Installs a ZFS root pool on a single disk. You can use the fdisk partition menu during the installation to partition the disk for your environment.

  • Text installation (SPARC and x86) – Installs a ZFS root pool on a single disk from media or over the network. You can use the fdisk partition menu during the installation to partition the disk for your environment.

  • Automated Installer (AI) (SPARC and x86) – Automatically installs a ZFS root pool. You can use an AI manifest to determine the disk and the disk partitions to be used for the ZFS root pool.

• Swap and dump devices – Automatically created on ZFS volumes in the ZFS root pool by all of the above installation methods. For more information about managing ZFS swap and dump devices, see Managing Your ZFS Swap and Dump Devices.

• Mirrored root pool configuration – You can configure a mirrored root pool during an automatic installation. For more information about configuring a mirrored root pool after an installation, see How to Configure a Mirrored Root Pool (SPARC or x86/VTOC).

• Root pool space management – After the system is installed, consider setting a quota on the ZFS root file system to prevent the root file system from filling up. Currently, no ZFS root pool space is reserved as a safety net for a full file system. For example, if you have a 68-GB disk for the root pool, consider setting a 67–GB quota on the ZFS root file system (rpool/ROOT/solaris) which allows 1 GB of remaining file system space. For information about setting quotas, Setting Quotas on ZFS File Systems.

ZFS Root Pool Requirements

Review the following sections that describe ZFS root pool space and configuration requirements.

ZFS Root Pool Space Requirements

When a system is installed, the size of the swap volume and the dump volume are dependent upon the amount of physical memory. The minimum amount of pool space for a bootable ZFS root file system depends upon the amount of physical memory, the disk space available, and the number of boot environments (BEs) to be created.

Review the following ZFS storage pool space requirements:

• For a description of memory requirements for the different installation methods, see Oracle Solaris 11.1 Release Notes.

• At least 7-13 GB of disk space is recommended. The space is consumed as follows:

  • Swap area and dump device – The default sizes of the swap and dump volumes that are created by the Solaris installation programs vary based on the amount of memory on the system and other variables. The dump device size is approximately half the size of physical memory or greater, depending on the system's activity.

    You can adjust the sizes of your swap and dump volumes to sizes of your choosing as long as the new sizes support system operation, during or after installation. For more information, see Adjusting the Sizes of Your ZFS Swap and Dump Devices.

  • Boot environment (BE) – A ZFS BE is approximately 4-6 GB. Each ZFS BE that is cloned from another ZFS BE doesn't need additional disk space. Consider that BE size will increase when the BE is updated, depending on the updates. All ZFS BEs in the same root pool use the same swap and dump devices.

  • Oracle Solaris OS Components – All subdirectories of the root file system that are part of the OS image, with the exception of /var, must be in the root file system. In addition, all Solaris OS components must reside in the root pool with the exception of the swap and dump devices.

ZFS Root Pool Configuration Requirements

Review the following ZFS storage pool configuration requirements:

• In Oracle Solaris 11.1, the disk that is intended for the root pool can have either an EFI (GPT) or SMI (VTOC) on an x86 based system or an SMI (VTOC) label on a SPARC system.

  • SPARC systems with updated GPT aware firmware will install an EFI (GPT) disk label on the root pool disk or disks. If the SPARC system does not have updated firmware, an SMI (VTOC) disk label is installed on the root pool disk or disks.

  • An x86 based system is installed with an EFI (GPT) label on the root pool disk or disk, in most cases.

  For information about what the EFI (GPT) label looks like on an x86 based system, see Using Disks in a ZFS Storage Pool.

• The pool must exist either on a disk slice or on disk slices that are mirrored if an SMI (VTOC) label disk on a SPARC based system or an x86 based system. Or, if the root pool disks are EFI (GPT) labeled, the pool can exist on a whole disk or mirrored whole disks. If you attempt to use an unsupported pool configuration during a beadm operation, you will see a message similar to the following:

  ERROR: ZFS pool name does not support boot environments

  For a detailed description of supported ZFS root pool configurations, see Creating a ZFS Root Pool.

• On an x86 based system, the disk must contain a Solaris fdisk partition. A Solaris fdisk partition is created automatically when the x86 based system is installed. For more information about Solaris fdisk partitions, see Guidelines for Creating an fdisk Partition in Oracle Solaris 11.1 Administration: Devices and File Systems.

• Pool properties or file system properties can be set on a root pool during an automatic installation. The gzip compression algorithm is not supported on root pools.

• Do not rename the root pool after it is created by an initial installation. Renaming the root pool might cause an unbootable system.