Go to main content

Transitioning From Oracle® Solaris 10 to Oracle Solaris 11.3

Exit Print View

Updated: December 2018

File System Changes

The file systems in Oracle Solaris 11 are very similar to Oracle Solaris 10 file systems. The following table describes the file systems that are supported in this release.

Table 5  File Systems That Are Supported in Oracle Solaris 11
File System Type
Supported File Systems
Disk-based file systems
Network-based file systems
Virtual file systems
Temporary file system
Loopback file system
Process file system.

    The general file system differences are as follows:

  • CacheFS is not available in Oracle Solaris 11.

  • ZFS is the default root file system.

  • UFS is a supported legacy file system, but it is not supported as a bootable root file system.

  • The legacy Solaris Volume Manager product is supported, but you cannot boot from a Solaris Volume Manager root device.

  • ZFS uses a separate ZFS volume for swap and dump devices. UFS can use a single slice for both swap and dump devices.

Root File System Requirements

The root file system hierarchy is almost identical to systems that are running Oracle Solaris 10 with a ZFS root file system. A ZFS root pool contains a ZFS file system with separate directories of system-related components, such as etc, usr, and var, that must be available for the system to function correctly.

  • After you install a system, the root of the Oracle Solaris file system is mounted, which means files and directories are accessible.

  • All subdirectories of the root file system that are part of the Oracle Solaris OS, with the exception of /var, must be contained in the same file system as the root file system.

  • A separate /var file system is created automatically for a global zone and a non-global zone in Oracle Solaris 11.

  • A rpool/VARSHARE file system is mounted at /var/share by default. The purpose of this file system is to share file systems across boot environments so that the amount of space that is needed in the /var directory for all BEs is reduced.

    # ls /var/share
    audit  cores  crash  mail

    Symbolic links are automatically created from /var to the /var/share components previously listed for compatibility purposes. This file system generally requires no administration except to ensure that /var components do not fill up the root file system. During a system upgrade, it might take some time to migrate data from the original /var directory to the /var/share directory.

  • In addition, all Oracle Solaris OS components must reside in the root pool, with the exception of the swap and dump devices.

  • A default swap device and a dump device are automatically created as ZFS volumes in the root pool when a system is installed. You cannot use the same volume for both swap and dump devices. Also, you cannot use swap files in a ZFS root environment. See Swap and Dump Device Configuration Changes.

Mounting File Systems

    Review the following considerations when mounting file systems:

  • Similar to Oracle Solaris 10 releases, a ZFS file system is mounted automatically when it is created. No need exists to edit the /etc/vfstab file to mount local ZFS file systems.

  • If you want to create and mount a local legacy UFS file system to be mounted at boot time, you will need to add an entry to the /etc/vfstab file as in previous Oracle Solaris releases.

  • If you want to mount a remote file system at boot time, you will need to add an entry to the /etc/vfstab file and start the following service:

    # svcadm enable svc:/network/nfs/client:default

    Otherwise, the file system is not mounted at boot time.