Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 234 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
8-28 CLI Maintenance Guide
Error: CIFS operation failed with an
error indicating a filer fault.
(CIFS) The filer returned an unexpected error during the import,
and the error indicates a problem at the filer itself. The syslog
shows the specific error. (Use
show logs syslog
to read the
syslog, or
grep string logs syslog
to search for a specific string in
the syslog.) Check the filer itself and correct the problem there.
After you correct the error, retry the import.
Error: CIFS write check failed.
(CIFS) The namespace software attempted to write a test file to
the share and failed. Go to the filer and check permissions for
the namespace’s
proxy-user (gbl-ns)
; the proxy user must be part
of the Backup Operators group on the filer.
Error: Cannot find credentials for
connection to filer.
(CIFS) Proxy user credentials have not been properly configured
for the CIFS share. These credentials must be a username and
password from the Backup Operators group. Note that they must
be configured as part of the Backup Operators group
at this filer ;
it is possible for a user to have different permissions on different
filers.
Use the
proxy-user
command to add or edit these credentials,
and use the
proxy-user (gbl-ns)
command to apply them to a
namespace.
Error: Collision rename failed due to
open file on share.
(CIFS) The share had a file that collided with an
already-imported file, and the volume failed to rename it
because a CIFS application has it open and locked.
You can use
show cifs-service open-files
to find the open file,
close cifs file
to close it, and then retry the share import.
Table 8-1. Share Status Conditions (Continued)
Status Condition Description/Action