Acopia Adaptive Resource Switch Cli Maintenance Manual page 94

Metadata Utilities: nsck and sync
Finding Metadata Inconsistencies
bstnA6k(gbl)# end
bstnA6k# nsck medarcv report inconsistencies norecurse
Scheduling report: inconsistencies.15.rpt on switch bstnA6k
bstnA6k# show reports inconsistencies.15.rpt
**** Inconsistencies Report: Started at Fri May 11 03:51:24 2007 ****
**** Software Version: 2.05.001.10153 (May
**** Hardware Platform: ARX-6000
**** Namespace: medarcv
**** Volume: /rcrds
**** Path: /rcrds
**** norecurse flag specified
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.
5-14
1. The start time, namespace, volume, and path for the report.
2. A table of shares that were examined, along with the IP of the back-end filer and
the share name at the filer.
3. A legend of keys for various types of metadata inconsistency. These keys are
used in the next table.
4. A table of files with metadata inconsistencies. For each file, the table shows
a. - a list of the file's inconsistencies (shown as keys from the legend
Type
above),
b. - the name of the filer-share with the inconsistent file, and
Share
c. - the exact path of the file on the share, relative to the share's root.
Path
5. A summary list with various totals.
For example, the following command sequence finds a missing file in the medarcv
namespace (highlighted in bold text):
Physical Filer
----------------------------------------------------------
] 192.168.25.29:prescriptions
] 192.168.25.20:histories
] 192.168.25.27:bulkstorage
9 2007 17:40:54) [nbuilds]
CLI Maintenance Guide