Table of ContentsView in Frames

Attribute cache timeouts

When data is retrieved from the origin volume, the file that contains that data is considered valid in the FlexCache volume as long as a delegation exists for that file. If no delegation exists, the file is considered valid for a certain length of time, specified by the attribute cache timeout.

If a client requests data from a file for which there are no delegations, and the attribute cache timeout has been exceeded, the FlexCache volume compares the file attributes of the cached file with the attributes of the file on the origin system. Then one of the following actions is taken:
With attribute cache timeouts, clients can get stale data when all of the following conditions are true:
Note: Clients can get stale data when a file on the origin volume is added to or removed from a directory that is already stored on the FlexCache volume. The file addition or deletion does not become visible on the FlexCache until the length of time specified in the directory attribute cache timeout (acdirmax) has passed since the last time the directory was updated on the FlexCache volume.

To prevent clients from ever getting stale data, you can set the attribute cache timeout to 0. However, this negatively affects your caching performance, because every data request for which there is no delegation causes an access to the origin system.

The attribute cache timeouts are determined by using volume options. The option names and default values are outlined in the following table:
Volume option Description Default value (seconds)
acdirmax Attribute cache timeout for directories 15s
acregmax Attribute cache timeout for regular files 15s
acsymmax Attribute cache timeout for symbolic links 15s
actimeo Attribute cache timeout for all objects 15s
For more information about modifying these options, see the na_vol(1) man page.