Finding Metadata Inconsistencies - Acopia Adaptive Resource Switch Cli Maintenance Manual

Metadata Utilities: nsck and sync

Finding Metadata Inconsistencies

Finding Metadata Inconsistencies
5-12
• Some customers prefer to perform restore operations directly on their back-end
filers.
Whenever a managed-volume client tries to access a file that has been removed by
one of the above operations, the client system reports an internal error. For CIFS
operations, messages appear in the syslog (labeled UNXFINDNONE, UNXNOPATH,
UNXOPENTYPE and/or UNXCRETYPE.), and the namespace software sends an
SNMP trap (vcifsNotfound or vcifsTypeMismatch). Use
a string. (The syslog is rotated regularly; use
files, including backups.)
To find the exact scope of metadata inconsistency, use the
command described below.
The
nsck report inconsistencies
a report. Metadata inconsistencies occur when a client is connected directly to a
back-end share and performs writes or deletes through that direct connection. Without
the ARX in the data path, the switch has no knowledge of the changes and cannot
update its metadata.
invalid
client
show logs
utility detects metadata inconsistencies and produces
servers
Acopia
valid clients
to search the syslog for
grep
for a complete list of all log
nsck report inconsistencies
CLI Maintenance Guide