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
Parameters
The following is the syntax for the vxfs_fcl_seektime() function:
int vxfs_fcl_seektime(void *handle, struct fcl_timeval time)
The function parameters are as follows:
*handle is a valid handle returned by a previous call to vxfs_fcl_open
time is an fcl_time_t structure type defined as follows:
struct fcl_time { uint32_t tv sec; unit32_t tv_nsec; } fcl_time t;
Note:
The time specified in fcl_time_t is in seconds or nanoseconds, while the time that is returned by a standard system call such as gettimeofday may be in seconds or microseconds. Therefore, a conversion may be needed.
vxfs_fcl_seektime assumes that the entries in the FCL are in a non-decreasing order of the time-stamps and does a faster-than-linear (binary) search to determine the FCL record with a time-stamp greater than the specified time. This means that vxfs_fcl_seektime can seek to a different record when compared to a seek done through a linear search. As a result, the vxfs_fcl_seektime interface is not 100% reliable.
The time-stamps in the FCL might be out-of-order under the following circumstances:
If the system time is modified
If the FCL file is on a cluster-mounted file system and the times on the different nodes are out-of-sync
Warning:
On a cluster file system, you must use a mechanism to keep the system clocks in sync (for example, Network Time Protocol - NTP), to help ensure that the vxfs_fcl_seektime interface is kept reasonably accurate.