Table of Contents
Advertisement
Type
-------------------------
[
NF CC
...
[
[
...
CLI Maintenance Guide
The directory renames follow the pattern below. The volume replaces each
unmappable CIFS character with its numeric equivalent:
new-dirname_share-jobid[-index][.ext]
where new-dirname is the original CIFS-side name, but with "(U+nnnn)" in place
of each unmappable character. The nnnn is the Unicode number for the character,
shown in hexadecimal format. The name is truncated if it exceeds 256 characters.
For example, "dir(U+30D2)(U+30AA)_myshare-2."
The share's import report includes the original name and the new name for each
renamed directory. The directory does not appear in the inconsistencies report, as its
new name is legal in both protocols.
Split Directories (SP)
Any NFS-only directory is called a split directory. All descendents of split directories
are flagged with an "SP" in the inconsistencies report; they are flagged because they
are inaccessible to CIFS clients. For example, here is a split directory and its
descendents:
Share
--------------------
]
[shr1-old
SP]
[shr1-old
SP]
[shr1-old
"Marked" Directories
Some multi-protocol directories are marked in the metadata for FGN-collision
checking. A directory is marked for this processing if it contains entries with either of
the following name issues:
•
NFS-only (such as "my?dir," or "MYDIR" and "mydir" together), and/or
•
matching an FGN pattern (such as "my~dir").
Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
Path
-------------------------------
]
/tools
]
/tools/extractCdDocs.pl
]
/tools/cleanBU.csh
8-69
Advertisement
Table of Contents
Troubleshooting
