Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 271 / 324

Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
CLI Maintenance Guide 8-65
Case-Blind Collisions (CC)
A case-blind collision occurs when two or more entries in the same parent directory
have names that differ only in case (for example, “index.html” and “INDEX.html”).
CIFS does not support case collisions, but NFS does. These are created by NFS
clients, either before import or while the volume is in service.
A file with a case-blind collision is marked with a “CC” in the inconsistencies report.
For example (from the inconsistencies report above):
Type Share Path
------------------------- -------------------- -------------------------------
...
[ NF
CC ] [shr1-old ] /INDEX.html
[ NF CC ] [shr1-old ] /index.html
Names with Characters that are Illegal in CIFS (IC)
The following characters are legal in NFS filenames but illegal in their CIFS
counterparts: any control character, /, \, :, *, ?, >, <, ”, or |. Files and directories with
illegal CIFS characters are NFS-only. Like case collisions, these are created by NFS
clients.
Each entry with illegal CIFS characters is flagged with an “IC” (for “Illegal
Character”) in the inconsistencies report. For example, this file is NFS-only because
of the colon (:) in its name:
Type Share Path
------------------------- -------------------- -------------------------------
...
[ NF
IC ] [shr1-old ] /stats/on_the_job:2004.cnv
If a directory contains more than 1,024 case collisions, its parent directory incurs an
additional performance penalty if it checks for FGN collisions during share import, a
restore data
operation,
nsck
operations, and
sync
operations. The FGN-collision check
was described in “Performance Issues” on page 8-61 .