Table 8-1. Share Status Conditions (Continued)
Status Condition
Error: Failed to create a file/directory
on filer.
Error: Failed to create directory
collision due to open CIFS file in path.
Error: Failed to find valid mount
version during import scan.
Error: Failed to mount filer during
import scan.
Error: Failed to open NFS connection
to filer during import scan.
CLI Maintenance Guide
Description/Action
This may indicate a full disk on the back-end filer or permissions
problems. Use the
show exports
permission settings at the filer.
Use the following guidelines for permissions problems:
•
For NFS exports, check your back-end filer configuration:
the back-end share should allow root access to all of the
ARX's proxy IP addresses. Use the
command to list all configured proxy IP addresses.
•
For CIFS shares, the switch uses the namespace's proxy user
as its identity. The proxy user, created by the
command, must belong to the Backup Operator's group at
this filer; each filer has a unique Backup Operator's group.
The
proxy-user (gbl-ns)
namespace.
(multi-protocol) A directory on this back-end share has a case
collision with an already-imported directory, and a CIFS client
has a file open in the already-imported directory. For example,
suppose the volume imports /vol/mydir from one share, a client
connects and opens a file in that share (/vol/mydir/myfile.exe),
and then the volume attempts to import a second share with
/vol/MYDIR. The volume must mark the first share as
"NFS-only" for the import to proceed, but cannot as long as the
client holds "myfile.exe" open. The second share therefore fails
its import.
You can use
show cifs-service open-files
to close it, and then retry the share import.
close cifs file
(NFS) These errors indicate an NFS-server problem at the filer.
Troubleshooting Managed Volumes
Correcting Share-Import Errors
command examine all
show ip proxy-addresses
command sets the proxy user for a
to find the open file,
proxy-user
8-33