HP CIFS Client A.01.09 Administrator's Guide, August 2003

Configuration File
Configuration Variables
Chapter 790
lookupStrategy As you probably know, the HP CIFS
Client maps between NFS requests
and SMB/CIFS requests. On the NFS
side, files are referenced by unique
identifiers, called NFS file handles.
On the HP CIFS side, files are
referenced simply by their path. The
HP CIFS Client must be able to
determine the path given to an NFS
file handle. There are two strategies
available to do this:
• pseudoInode
This strategy derives the NFS file
handle as a hash value from the
path. The hash is chosen in a way
that makes efficient lookups
possible, as long as the depth of
the file in the directory hierarchy
is lower than 27. The advantage
of this strategyis the lowmemory
consumption: Files can be looked
up on demand, nothing has to be
stored. The main disadvantage is
that NFS file handles change
when files are renamed. This
leads to a conflict with Unix
semantics when open files are
renamed: After renaming, the
handle of the open file is stale
and the file can not be accessed
without reopening. It also
conflicts with a bug in the caching
code of the Solaris NFS client
where the writeback occurs only
after closing the file, not during
closing the file.
• database
In this strategy all NFS file
handle to file path relations are
stored in an internal database.