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
Recorded changes
The File Change Log records the following file system changes:
Creates
Links
Unlinks
Renaming
Data appended
Data overwritten
Data truncated
Extended attribute modifications
Holes punched
Miscellaneous file property updates
Note:
The FCL is supported only on disk layout Version 6 and later.
The FCL stores changes in a sparse file, referred to as the FCL file, in the file system namespace. The FCL file is always located in /mount_point/lost+found/changelog
. The FCL file behaves like a regular file, however, some user-level operations are prohibited, such as writes. The standard system calls open(2), lseek(2), read(2) and close(2) can access the data in the FCL file. All other system calls such as mmap(2), unlink(2), and ioctl(2) are not allowed on the FCL file.
Warning:
For compatibility with future VxFS releases, the FCL file might be pulled out of the namespace, and these standard system calls may no longer work. Therefore, Veritas recommends that all new applications be developed using the programmatic interface.