Acopia Adaptive Resource Switch Cli Maintenance Manual page 244

Troubleshooting Managed Volumes
Correcting Share-Import Errors
Table 8-1. Share Status Conditions (Continued)
Status Condition
Error: Maximum number of
namehash collisions for a filename
reached in a directory.
Error: Maximum Path Length
Exceeded
Error: Metadata database I/O failure.
8-38
Description/Action
A directory in this share has too many entries (files and/or
subdirectories) whose names differ only in case (for example,
"thisFile.txt," "THISfile.txt," "thisFILE.txt," and so on). The
limit on case collisions for a single entry name is over 16,000. A
client tried to create a new entry that would exceed the limit for a
particular entry name, and the volume blocked the action with an
"access denied" error.
You can resolve this issue by accessing the volume as a client
and moving as many of the file entries as possible. Create a new
directory to hold many of them, or rename them to an
non-matching name. For example, you could change the earlier
examples to "thatFile.txt," "THATfile.txt," and so on to stop
them from making a case-insensitive match with "thisfile.txt."
The specific directory and filename appears in a syslog message
labeled "ERROR_MAX_HASH_COLLISIONS." Use
ERROR_MAX_HASH_COLLISIONS logs syslog
this error in the syslog.
Note that the colliding names are usually case collisions, but not
always. The collision occurs after a mathematical conversion of
the filenames, called a hash.
A path to one of the files exceeds the maximum, 1024
characters.
There was a database I/O failure for the share. This may be
caused by a transient network error, or a filer problem. You can
use the command to check the filer and connection
show exports
for common problems.
Once the external problem is resolved, remove the share from
the volume, add it back, and retry the import.
grep
to search for
CLI Maintenance Guide