With VisionFS, each file or directory effectively has three names:
When a long or short name is used in Windows, VisionFS uses the correct UNIX filename.
Potentially, there are fewer long names than UNIX filenames, and fewer short names than long names. This means that the process of converting UNIX filenames to long names, then to short names, might result in two unique UNIX filenames losing their uniqueness. VisionFS ensures that this can't happen by adding unique suffixes to the basename where a clash would occur.
This involves the following steps:
This involves the following steps:
To make a set of clashing long or short names unique, VisionFS first generates a 32-bit checksum for each, based on the original UNIX filename. The checksum is converted to a printable form.
Then, a suffix is formed for each clashing name, using the special character for the share (by default, ~) and the last character of the printable checksum (or however many characters are needed to form unique suffixes for all clashing names).
Finally, the suffixes are added to the basenames of the clashing names, replacing the last 2 (or more) characters to ensure the basenames don't exceed 8 characters in length.
By default, if basenames are unique when truncated to 8.3 format, then no changes are made -- a unique suffix isn't needed. In some cases, you might want VisionFS to always use a suffix when truncating. The Profile Editor lets you do this, using the ``Always use in truncated filenames'' box on the Files tab of a share's properties.