Upgrading With Disk Space Reallocation

The upgrade option in the Solaris Web Start installation method, the Solaris suninstall program, and the custom JumpStart program provide the ability to reallocate disk space. You can reallocate disk space if the current file systems do not have enough space for the upgrade. File systems might need more space for the upgrade for the following reasons:

• The Solaris software group that is currently installed on the system contains new software in the new release. Any new software that is included in a software group is automatically selected to be installed during the upgrade.

• The size of the existing software on the system has increased in the new release.

The auto-layout feature attempts to reallocate the disk space to accommodate the new size requirements of the file system. Initially, auto-layout attempts to reallocate space, based on a set of default constraints. If auto-layout cannot reallocate space, you must change the constraints on the file systems.

Auto-layout does not have the ability to grow file systems. Auto-layout reallocates space by backing up required files on the file systems that need to change, repartitioning the disks on the basis of the file system changes, and restoring the backup files before the upgrade happens.

• If you are using the Solaris Web Start program, and auto-layout cannot determine how to reallocate the disk space, you must use the Solaris suninstall program or the custom JumpStart program to upgrade.

• If you are using the Solaris suninstall program, and auto-layout cannot determine how to reallocate disk space, you must specify the file systems that can be moved or changed and run auto-layout again.

• If you are using the custom JumpStart method to upgrade and you create an upgrade profile, disk space might be a concern. If the current file systems do not contain enough disk space for the upgrade, you can use the backup_media and layout_constraint keywords to reallocate disk space. For an example of how to use the backup_media and layout_constraint keywords in a profile, refer to Example 26–5.