Veritas™ File System Programmer's Reference Guide - Solaris
- Veritas File System software developer's kit
- File Change Log
- About the File Change Log file
- Record types
- File Change Log tunables
- Application programming interface for File Change Log
- API functions
- File Change Log record
- Copying File Change Log records
- Veritas File System and File Change Log upgrade and downgrade
- Reverse path name lookup
- Multi-volume support
- Named data streams
- Veritas File System I/O
- Caching advisories
- Extents
- Thin Reclamation
File Change Log logging activation
By default, FCL logging is deactivated and can be activated on a per-file system basis using the fcladm command.
See the fcladm(1M) manual page.
When FCL loggin is activated, new FCL records are appended to the FCL file as file system changes occur. When FCL logging is turned off, further recording stops, but the FCL file remains as /lost+found/changelog
. You can only remove an FCL file by using the fcladm command.
The FCL file has an associated version that represents the layout or is the internal representation of the FCL file, along with the list of events recorded in the FCL file.
Whenever a new version of VxFS is released, the following occurs:
There may either be additional events recorded in the FCL file
The internal representation of the FCL file may change
This results in the FCL file version getting updated. For example, in VxFS 4.1, the default was Version 3. However, because VxFS 5.0 and later releases record additional sets of events that are not available in Version 3 (such as file opens), the default version in VxFS 5.0 and later releases is 4. To provide backward compatibility for applications developed on VxFS 4.1, VxFS 5.0 and later releases provide an option to specify an FCL version during activation. Depending on the specified version, the logging of the new record types is either allowed or disallowed.
The logging of most of the newly added records in VxFS 5.0 and later releases, such as file opens and I/O statistics, is optional and is turned off by default. Recording of these events can be enabled or disabled using the [set] and [clear] options of the fcladm command.
The FCL meta-information comprising of the file system state, version, and the set of events being tracked is persistent across reboots and file system unmounts or mounts. The version and event information is also persistent across re-activations of FCL logging.