Managing Namespace Collisions - Acopia Adaptive Resource Switch Cli Maintenance Manual

Managing Namespace Collisions

CLI Maintenance Guide
When a managed volume is enabled, the ARX takes inventory from all of the
volume's back-end shares and includes their files into the volume. An important part
of this process is to ensure that there is only a single instance of any given
path/filename. If you have a path/filename that is identical on more than one back-end
share, there is an import collision; only one of the files can be imported into the
managed volume. The redundant file is renamed as follows:
filename_share-jobid.ext
where
filename is the file's original name, without its extension (for example,
"myfile" from "myfile.doc"),
share is the name of the namespace share,
jobid is an integer identifying the job that imported the share, and
.ext is the files original extension (for example, "doc"), if there is one.
If there is more than one redundant file, an index is added:
filename_share-jobid-index.ext
where index is a number starting at 1.
The same naming conventions are applied to a directory whose name matches an
already-imported file, or to a directory that has different file attributes than an
already-imported directory. In addition, any tilde (~) characters in a directory name
are replaced with commas (,).
Troubleshooting Managed Volumes
Managing Namespace Collisions
8-53