NFS Gateway high utilization and/or directories don't show some files.

NFS Gateway expriences high utilization and/or directories don't show some files.

High utilization occurs for about 30 seconds when certain directory lists are obtained through an NFS Gateway volume.

Some files are not appearing in directory lists on an NFS Gateway volume.

Some files that exist on a remote NFS Server are not displayed in a directory list given through the NFS Gateway volume.

NFS Gateway uses Btrieve to manage it's local meta-data (shadow cache, shadow files). When Btrieve searches, it only uses the first 32 characters of the submitted search term. If 2 or more files exist with lengthy names, and the first 32 characters of those names are exactly identical, Btrieve may return the wrong entry (first found). This could cause missing entries as well as significant corruption to the NFS Gateway volume's meta-data.

This is a rare issue, as multiple file names with the first 32 characters identical are not encountered frequently.

A fix is present in in NFS Gateway SP4 (which is to be used with NetWare 6.5 SP6). The updated NFS Gateway will verify that the data returned by Btrieve is for the actual file being looked up, when dealing with file names over 32 characters. If it does not match, NFS Gateway will request the next match, and so forth.

For those who cannot yet update to NetWare 6.5 SP6, a fix has been released in NFSGY655A.EXE and NFSGY655B.EXE. Which file is needed depends on which version on NSS is in use. Check the readmes for those NFSGY* down files (available at https://support.novell.com/filefinder) for NSS version details. These files will likely only be available for a limited time.