2N/A# The contents of this file are subject to the terms of the
2N/A# Common Development and Distribution License (the "License").
2N/A# You may not use this file except in compliance with the License.
2N/A# See the License for the specific language governing permissions
2N/A# and limitations under the License.
2N/A# When distributing Covered Code, include this CDDL HEADER in each
2N/A# If applicable, add the following below this CDDL HEADER, with the
2N/A# fields enclosed by brackets "[]" replaced with your own identifying
2N/A# information: Portions Copyright [yyyy] [name of copyright owner]
2N/ACopyright (c) 2011, Oracle
and/or its affiliates. All rights reserved.
2N/AZones Dataset Conversion
2N/AIf zones were installed on Oracle Solaris 11 Express 2010.11, a conversion
2N/Aprocess is required to make use of them on this release of Oracle Solaris
2N/A11. This conversion process is described in this README.
2N/A NOTICE: The conversion process is a one way operation. Once a zone is
2N/A converted to the new dataset layout it will not be bootable
2N/A in with Solaris 11 Express 2010.11.
2N/AThis README applies to solaris branded zones and solaris10 branded zones
2N/A(Oracle Solaris Containers) on Oracle Solaris 11.
2N/AOracle Solaris 11 enhances the layout of ZFS datasets in each zone to more
2N/Aclosely resemeble the layout found in the global zone. The key aspects of
2N/Athis enhancement include:
2N/A - Each zone has a delegated dataset that is manageable by the zone
2N/A administrator. The existence of this dataset does not limit the use of
2N/A other delegated datasets.
2N/A - The default layout of this delegated dataset is as follows. Notice that
2N/A it has some components that are unique to each boot environment and
2N/A others that are shared by each boot environment.
2N/A <zonepath dataset>/rpool
2N/A This is the delegated dataset, referred to as the "zone rpool
2N/A dataset." It is mounted within the zone at /rpool. Aside from the
2N/A datasets within the "zone ROOT dataset," all filesystem and volume
2N/A datasets created within the "zone rpool dataset" are shared across
2N/A all of this zone's boot environments.
2N/A This dataset contains boot environments and is referred to as the
2N/A "zone ROOT dataset." Each dataset created directly within the zone
2N/A ROOT dataset represents the root (/) of a zone boot environment.
2N/A Zone boot environments should be created and destroyed with the
2N/A zoneadm(1M) and beadm(1M) commands.
2N/A global zone. They are shared among all of a single zone's boot
2N/A These datasets are not created if there exist zonecfg "fs" or
2N/A "dataset" resources that would cause a mount anywhere under the
2N/AThe conversion process updates the zone dataset layout from the format found
2N/Ain Oracle Solaris 11 Express 2010.11 to that used by Oracle Solaris 11. The
2N/Aconversion process includes:
2N/A - Create the zone's <zonepath dataset>/rpool dataset.
2N/A - Move the zone's boot environments from the <zonepath dataset>/ROOT
2N/A - Create the zone's <zonepath dataset>/export and <zonepath
2N/A is not performed if the zone's configuration includes "fs" or "dataset"
2N/A resources. See zonecfg(1M) for details on those resources.
2N/AFile systems and datasets that are mounted in the zone via zonecfg resources
2N/Aare not affected. They will continue to be mounted at the same location as
2N/Athey had before the conversion. Data will not be migrated from those file
2N/ATo convert a zone to the new dataset layout, run dsconvert with the name of
2N/Athe zone. Additional options are available for dry-run and verbose output.
2N/ARun "dsconvert -h" for a complete usage statement.
2N/ADepending on whether the zone was previously attached or detached, dsconvert
2N/Awill give advice for any steps required to make the zone bootable.
2N/AUpon completion of the conversion process, "zoneadm -z <zone> verify" will be
2N/Arun. If it detects configuration that was not able to be automatically
2N/Aconverted, you will need to manually complete this conversion before the