Table of Contents
Advertisement
Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
8-66
Client View: Acopia-Generated Names
A managed volume creates its own Acopia-generated names (AGNs) for files or
directories with illegal CIFS characters. The volume presents the AGN to its CIFS
clients. The AGN has a unique format, easily distinguishable from the formats of any
FGNs:
(!) nnn_changed-filename
Where
•
''(!) '' (with the trailing space) is the prefix for all AGNs.
•
nnn is a different number for every AGN in this directory. This number is
padded so that it is always at least three digits long.
•
changed-filename is the original filename (or directory name), with all
illegal characters replaced with an underscore character (_).
For example, the above NFS-side filename ("on_the_job:2004.csv") may have the
following AGN for CIFS clients:
(!) 001_on_the_job_2004.cnv
The ARX only generates CIFS-side AGNs. NFS-side AGNs are not possible in the
current implementation.
Names That Resemble FGNs (FN)
Whenever a client creates a primary name with an FGN pattern (for example,
"NEWFL~1.DOC"), it may collide with an actual FGN on a back-end filer. This has a
performance impact; if the name should migrate or replicate from one share to
another, the volume must first probe the target share to confirm that there are no
actual FGNs that collide with it.
CLI Maintenance Guide
Advertisement
Table of Contents
Troubleshooting
