Veritas™ File System 5.0.1 Programmer's Reference Guide

Table 2-2
FCL record structure fields (continued)
ValidityDescriptionField
Valid for all FCL records except
for event mask changes and
unlinks. For event mask changes,
the inode number and generation
count are implicit. For unlink, the
generation count is not needed to
get the filename via reverse name
lookup, since it is already present
with the record.
The generation count of the
changed file. The generation count
in combination with the inode
number (of the file) is passed to
vxfs_inotopath_gen to provide
the exact full path name of the
object. Without the generation
count, the returned path name can
be a re-used inode.
fr_inogen
Valid when the FCL record is
VX_FCL_UNLINK,
VX_FCL_RENAME or
VX_FCL_LINK. The unlink and
rename; filename and the parent
inode number; and generation
count, contain information about
the old file that was removed. For
the link, they represent the new
filename.
For FCL records like file remove
or rename, where the directory
entry is removed, the filename
cannot be determined by reverse
name lookup. Similarly in the case
of link record, the filename cannot
be determined unambiguously.
Therefore in these cases, the
filename, inode number, and
generation count of the parent
directory (containing the file being
changed) is recorded. The parent
directory inode (fr_pinonum) and
generation count (fr_pinogen)
can be used with the reverse name
lookup API to identify the full path
name of the parent directory.
Adding the trailing filename yields
the object’s full name.
fr_pinonum
fr_pinogen
fr_filename
Valid only when the FCL record is
VX_FCL_FILEOPEN.
A short name of the command
which opened the file represented
by fr_inonum and fr_inogen.
fr_cmdname
File Change Log
Application programming interface for File Change Log
42