Acopia Adaptive Resource Switch, Руководство по обслуживанию CLI

Страница: 273 / 324

Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
CLI Maintenance Guide 8-67
An FGN pattern typically follows the “8.3” model; recall “The ‘8.3’-FGN Pattern” on
page 8-58 . The exception is on EMC file servers, where the base name may exceed 8
characters. Whenever an EMC file server generates a long FGN, the base name ends
with a tilde (~) followed by a number:
long-base-name ~ n [.[ ext ]]
An entry is NFS-only if it matches the FGN pattern and collides with an actual FGN.
These entries are marked with an “FN” (for “Filer-generated Name”) in the
inconsistencies report; they have an additional “NF” flag if they collide with a real
FGN. For example, these three entries all match the FGN pattern but do not collide:
Type Share Path
------------------------- -------------------- -------------------------------
...
[ FN ] [shr1-old ] /POLICI~2
[ FN ] [shr1-next ] /Y2KCLA~4
[ FN ] [shr1-next ] /Y2KCLA~1
[ FN ] [shr1-next ] /OVERDU~1.DOC
Unicode Characters in CIFS Names: Non-Mappable in NFS
(NM)
Some illegal file or directory names may have been created by CIFS clients before
import. CIFS natively supports Unicode characters in its file or directory names, but
NFS servers must specifically have their character encoding configured to support
them. Otherwise, the Unicode characters are
non-mappable to NFS. A multi-protocol
filer set for Latin1 character encoding may have allowed CIFS clients to use Unicode
characters (such as Korean or Japanese characters) in entry names. If so, the filer
accepted the CIFS name and created an FGN for its NFS clients.
CIFS clients cannot create this problem through the volume; the volume only allows
CIFS-side names that are fully mappable to NFS. This is an import-only issue.
When the volume imports the share, it treats non-mappable names differently for files
and directories.
An FGN-patterned name can collide with an 8.3 FGN as well as one of the
multi-protocol FGNs.