File-System Logging

Logging is required for UFS and VxFS cluster file systems. This requirement does not apply to QFS shared file systems. Sun Cluster software supports the following choices of file-system logging:

• Solaris UFS logging – See the mount_ufs(1M) man page for more information.

• (Solaris 9 only) SPARC: Solaris Volume Manager transactional-volume logging – See Transactional Volumes (Overview) in Solaris Volume Manager Administration Guide for more information.

  ---

  Note –

  Solaris Volume Manager transactional-volume logging is removed from the Solaris 10 OS. Solaris UFS logging provides the same capabilities but superior performance, as well as lower system administration requirements and overhead.

  ---

• SPARC: VERITAS File System (VxFS) logging – See the mount_vxfs man page provided with VxFS software for more information.

The following table lists the file-system logging supported by each volume manager.

SPARC: On the Solaris 9 OS, consider the following points when you choose between Solaris UFS logging and Solaris Volume Manager transactional-volume logging for UFS cluster file systems:

• Solaris UFS logging always allocates the log by using free space on the UFS file system, and depending on the size of the file system.

  • On file systems less than 1 Gbyte, the log occupies 1 Mbyte.

  • On file systems 1 Gbyte or greater, the log occupies 1 Mbyte per Gbyte on the file system, to a maximum of 64 Mbytes.

• A transactional volume manages UFS logging. The logging device component of a transactional volume is a volume that you can mirror and stripe. You can create a maximum 1-Gbyte log size, although 64 Mbytes is sufficient for most file systems. The minimum log size is 1 Mbyte.