Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 250 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
8-44 CLI Maintenance Guide
Error: Storage-scan database is
corrupt or inaccessible.
(NFS) The ARX creates a temporary database during the import
process. The database was deleted while the import was
underway. This may indicate that other clients are bypassing the
ARX to access the share; this is an unsupported configuration.
Error: Storage-scan database is
corrupt.
Error: Unable To Connect to CIFS
Share.
The connection to the back-end CIFS share failed due to
possible configuration errors or a broken connection to the
back-end filer.
Error: Unable to read file due to stale
filehandle.
(NFS) The filer provided a filehandle in response to an earlier
NFS call, and is now pronouncing it “stale.” This is inconsistent
filer behavior; it may indicate that NFS clients are bypassing the
ARX to access the share. Check the filer share, correct the
problem there, and retry the import.
Error: Unresolvable case-blind name
collision.
(CIFS) A file on this share has the same name and path as a file
on an already-imported share, based on a case-blind comparison,
and the volume is configured with
no cifs case-sensitive
. That is,
some of the characters have differing cases, but the characters
match (for example, “index.htm” matches “index.HTM”). If the
volume is not case-sensitive, it cannot see the difference
between the two names.
You have three options to address this error:
• Manually go to the filer and rename the file.
• Set the
modify
flag on this volume. By setting the
modify
flag, you allow the volume to rename the file on import.
• Use
cifs case-sensitive
to make the volume case-sensitive.
Then retry the import.
Table 8-1. Share Status Conditions (Continued)
Status Condition Description/Action