Acopia Adaptive Resource Switch Cli Maintenance Manual page 93

CLI Maintenance Guide
A local process on the filer, such as anti-virus software, can cause an inconsistency by
removing or renaming a file.
You can use the
nsck report inconsistencies
full on a namespace, or to confirm that there are no inconsistencies at all.
nsck rebuild
From priv-exec mode, use the
current namespace's managed volumes for metadata inconsistency:
nsck name report inconsistencies [path] [share share-name]
[norecurse] [nofilehandles] [outputfile outputfile]
where:
name (1-30 characters) is the namespace on which to report. Use the
command for a list of configured namespaces.
namespace
path (optional, 1-256 characters) narrows the scope of the report to a specific
virtual path in the namespace (for example, '/home/jrandom'). This must be
a managed volume, or a path within a managed volume.
share share-name (optional, 1-64 characters) narrows the scope further, to a
single namespace share. This is the share's name in the namespace, not on
the filer.
norecurse (optional) specifies to not recurse into subdirectories during the
report.
nofilehandles (optional) specifies to not validate filehandles during a report.
outputfile outputfile (optional, 1-256 characters) specifies a prefix for a
customized filename (for example, 'jrandom_inconsistencies'), as opposed
to the default. Use the
maintenance directory.
You can run one nsck job at a time on a given namespace. Use
the progress of nsck jobs; see
page 5-2.
The CLI shows the report name after you invoke the command. Use
a full list of nsck reports, and use
contains the following information:
Metadata Utilities: nsck and sync
Finding Metadata Inconsistencies
to determine whether to run
nsck report inconsistencies
command to display the file in the
show reports
"Showing the Progress of nsck and sync Jobs" on
, , or
show tail grep
sync files
command to check the
show nsck
show reports
to view one report. The report
or a
show
to monitor
for
5-13