Identifying All '8.3' Collisions - Acopia Adaptive Resource Switch Cli Maintenance Manual

Identifying All '8.3' Collisions

bstnA6k# nsck medarcv report inconsistencies /rcrds outputfile rcrdsIssues
Scheduling report: rcrdsIssues.rpt on switch bstnA6k
bstnA6k# show reports rcrdsIssues.rpt
**** Inconsistencies Report: Started at Mon Apr 30 04:00:17 2007 ****
**** Software Version: 2.05.001.10144 (Apr 27 2007 17:42:08) [nbuilds]
**** Hardware Platform: ARX-6000
**** Namespace: medarcv
**** Volume: /rcrds
**** Path: /rcrds
Share
--------------------
[rx
[charts
[bulk
**** Legend:
**** LF = File exists in the metadata, but is missing from the physical filer.
**** LD = Directory exists in the metadata, but is missing from the physical filer.
**** FF = File exists on the physical filer, but is missing from the metadata.
**** FD = Directory exists on the physical filer, but is missing from the metadata.
**** IF = Filehandles in the metadata do not match the filehandles on the physical filer.
**** MF = The file is currently being migrated.
**** NL = Unable to lock parent directory during report.
**** FE = Error contacting filer during report.
**** FO = Filer Offline: The filer is offline or disabled.
**** F8 = A file name matches a CIFS alternate "8.3" name on another share.
**** D8 = A directory name matches a CIFS alternate "8.3" name; its contents will be
skipped.
CLI Maintenance Guide
If CIFS clients complain about access issues or slow performance, you should
identify the 8.3 collisions in the volume and work toward changing their names. This
is especially true for directory names, which may affect performance for files and
directories under them. Run an nsck-inconsistencies report (recall
Inconsistencies" on page
flagged with "F8," and each directory is flagged with "D8."
For example, this command sequence generates and shows an inconsistencies report
for the "medarcv" namespace, which reveals one file collision and one directory
collision (highlighted in bold text):
Physical Filer
----------------------------------------------------------
] 192.168.25.29:prescriptions
] 192.168.25.20:histories
] 192.168.25.27:bulkstorage
Troubleshooting Managed Volumes
Finding Collisions with CIFS '8.3' Names
5-12) to reveal all 8.3 collisions. Each file with this issue is
"Finding Metadata
8-59