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

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

Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
8-70 CLI Maintenance Guide
If the directory contains either of these name types, the volume must check for FGN
collisions every time a client creates a name of the
other type. The FGN-collision
check was described earlier, in “Performance Issues” on page 8-61 . This check occurs
for all types of clients, including the policy engine; that is, the volume also performs
extra checking before
migrating any FGN-related files or subdirectories from one
back-end share to another.
A directory remains “marked” for this checking even if clients remove all NFS-only
and FGN-matching entries from it. You can remove the mark by emptying the
directory completely, or by cleaning out all entries with FGN issues and running
sync
files
on it. The latter option is described later in this section.
Preventative Striping
Another disadvantage for a marked directory can be extra back-end copies (called
stripes ) for some of its NFS-only subdirectories. Before the policy engine migrates
any NFS-only file (such as “newFile” in a directory that already contains
“NEWFILE”), it stripes all of its subdirectories that fit an FGN pattern (such as
“DIR~3”) to the target share. Then it migrates the file. This ensures that the
subdirectories remain open to both CIFS and NFS. It also creates extra, unexpected
directory stripes on the back-end target share.
Correcting NFS-Only Entries
To remove the “NFS-only” flag from a file or directory, an NFS client can access the
volume’s front-end service and rename the offending entry from there. Choose a
name that is valid in both protocols. For example, here are some NFS-only issues and
possible solutions:
• Case collision (“index.html” and “INDEX.HTML” in the same directory)
Rename “INDEX.HTML” to “index2.html.”
• Illegal CIFS characters (“on_the_job:2004.csv”)
Rename to “on_the_job_2004.csv,” to eliminate the illegal colon (:).
• Name with an FGN pattern (“OVERDU~1.DOC”)
Rename to “overdue_1.doc” to remove the tilde (~).