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 file layout
In VxFS 4.1, the internal layout of the FCL file was exposed to the user and the applications were expected to access the FCL file using standard file system interfaces, such as open(2), read(2), and lseek(2). However, this methodology may lead to future compatibility issues, because if the underlying FCL layout and the FCL version changes, the application must be changed and recompiled to accommodate these changes.
VxFS 5.0 introduced a new programming interface that provides improved compatibility, even when the on-disk FCL layout changes. With this API, the FCL layout is not a concern for applications. Consequently, this section provides only a rudimentary description of the FCL layout.
The FCL file is usually a sparse file containing the FCL superblock and the FCL records. The first information block in the FCL file is the FCL superblock. This block may be followed by an optional hole as well as the FCL records which contain information about the changes in the file system.
Figure: FCL file format depicts the FCL file format.