1. Installing and Configuring an Oracle Solaris Cluster 4.4 Environment
  2. Planning the Oracle Solaris Cluster Configuration
  3. Planning Global Devices, Device Groups, and Cluster File Systems
  4. Mount Information for Cluster File Systems

Mount Information for Cluster File Systems

Consider the following points when you plan mount points for cluster file systems:

  • Mount-point location –By default, ZFS datasets are mounted under the zpool's root file system. For example, a ZFS pool named pool1 will have its file system datasets mounted on /pool1, /pool1/fs1, /pool1/fs2, and so on.

    In earlier releases of Oracle Solaris Cluster that did not support cluster file systems on ZFS, there was a convention of mounting cluster file systems under the /global directory to more easily distinguish them from the local file systems. With ZFS, it is possible to specify non-default mount points by executing the zfs set command on the ZFS dataset. However, the mountpoint of a ZFS file system dataset can be changed only while the dataset is not mounted globally. The ZFS command must be executed on the node where the ZFS pool is imported. To avoid dealing with non-default mountpoints, it is recommended to accept the default ZFS mounting behavior. For more information, see the zfs(8) man page.

  • Nesting mount points – ZFS datasets within a given ZFS storage pool may be nested. For example, a pool named globalpool might have file system datasets named globalpool/fs1, globalpool/fs2, globalpool/fs2/fs3, and so on. These file system datasets will be mounted on the corresponding paths under the pool's root file system /globalpool.

    Do not nest the mount points for non-ZFS cluster files systems. For example, do not set up one file system that is mounted on /global/a and another file system that is mounted on /global/a/b. Ignoring this rule can cause availability and node boot-order problems. These problems would occur if the parent mount point is not present when the system attempts to mount a child of that file system.

    An exception to this rule is for cluster file systems on UFS. You can nest the mount points if the devices for the two file systems have the same physical host connectivity, for example, different slices on the same disk.

    Note:

    This restriction still applies to Oracle HSM shared file systems even if the two file system devices have the same physical host connectivity.

    Mounting a local filesystem or an HA local filesystem on a global filesystem is not supported. Use symbolic links from the global filesystem to the non-global filesystem instead.

  • forcedirectio (UFS only) – Oracle Solaris Cluster software does not support the execution of binaries off cluster file systems that are mounted by using the forcedirectio mount option.