Acopia Adaptive Resource Switch Cli Maintenance Manual page 241

Table 8-1. Share Status Conditions (Continued)
Status Condition
Error: File exists in CIFS, but not in
NFS.
Error: filename collision.
Error: Filer does not have enough
free space to perform import.
Error: Filer does not provide an NFS
filehandle for a file in its directory
listing.
CLI Maintenance Guide
Description/Action
(multi-protocol) The share is configured for both NFS and CIFS,
but a directory that is visible in the back-end-CIFS share is not
found in the NFS export. The filer probably has two different
names for the directory: one for CIFS clients and one for NFS
clients.
Check the directory at the back-end share, and rename it so that
both versions have the same name. Alternatively, you can set the
flag on this volume. By setting the
modify
the volume to rename the directory on import. You may also
need to set
import rename-directories
share; this allows the volume to rename directories whose CIFS
names do not map to the character encoding for NFS. Then retry
the import.
A file on this share has the same name and path as a file on an
already-imported share. To fix this, you can manually go to the
filer and rename the file, or you can set the
volume. By setting the modify flag, you allow the volume to
rename the file on import. Then retry the import.
(NFS) The ARX creates a temporary database on each share
during the import process: there is not enough room on this share
to create the database. The database requires at least 100
MegaBytes of free space.
Clear some free space at the filer share, then restart the import.
(multi-protocol) The filer provided a filename in an NFS
READDIR call, but did not translate that filename into a
filehandle in a subsequent LOOKUP call. Some multi-protocol
filers behave this way when a CIFS filename has characters that
are not supported by NFS; the filer returns the UTF-8 version of
the filename for the READDIR call, which it later rejects in a
subsequent LOOKUP call. The ARX can see the file in the
directory listing, but cannot get access to the file itself.
Rename the file at the filer share, then restart the import.
Troubleshooting Managed Volumes
Correcting Share-Import Errors
modify
unmapped-unicode
modify
flag, you allow
for this
flag on this
8-35