Recursively Correcting Split Directories; Running Periodic Checks For Nfs-Only Entries - Acopia Adaptive Resource Switch Cli Maintenance Manual

bstnA6k(gbl)# end
bstnA6k# sync files insur volume /claims path / recurse
Scheduling sync files operation on switch bstnA6k, report name: sync.7._rcrds.rpt
bstnA6k# ...

Running Periodic Checks for NFS-Only Entries

CLI Maintenance Guide
You can correct a marked directory by correcting all of the NFS-only entries within it.
After the rename(s), you must run the
NFS-only flags from the volume's renamed files and directories. The sync utility
probes all of the volume's shares to confirm that no FGN collisions exist. This also
removes the marks from any directories that no longer contain any NFS-only entries.
The command was described in an earlier chapter: recall
sync files
Metadata with Actual Files" on page
For example, the following command sequence exits to priv-exec mode and
synchronizes the metadata in the "insur~/claims" volume:

Recursively Correcting Split Directories

In any split directories that have been corrected, the sync utility probes all child
entries, including child directories, for the first time. This may expose more NFS-only
entries and/or FGN-patterned names. If so, repeat the renaming and syncing process
as needed.
Best practices dictate that you occasionally run an inconsistencies report on your
multi-protocol volumes to monitor for NFS-only entries. Clients can create these by
using bad characters in file/directory names, making a pair of entries with a
case-collision, or by making an entry name that happens to match an FGN on one of
the volume's back-end filers. As described above, once a directory contains any
NFS-only or FGN-patterned entry, it performs extra processing for certain (rare)
client operations.
Troubleshooting Managed Volumes
Finding NFS-Only Entries in a Multi-Protocol Volume
sync files ... recurse
5-19.
command to remove the
"Synchronizing
8-71