Correcting Share-Import Errors - Acopia Adaptive Resource Switch Cli Maintenance Manual

Correcting Share-Import Errors

Table 8-1. Share Status Conditions
Status Condition
Error: A directory was removed from
the filer during import.
Error: A filename/directory could not
be mapped to the namespace
character encoding.
CLI Maintenance Guide
After you enable a namespace volume, the volume reads all of its back-end shares and
imports all of their files and directories. If anything goes wrong in any share, the
failed share shows a Status of "
of the errors in Table 8-1
(not
show namespace
Follow the suggestions in the table to find and fix the root cause of the error. Once the
error is corrected, retry the import.
The sections below the table describe various methods for either restarting the import
or removing the share.
A directory was found during an early scan of the filer share,
then later it was missing. Either a client or client application
must have accessed the filer directly (that is, not through this
managed volume) during the import.
This ARX cannot support unexpected changes to the back-end
shares during (or after) import.
One of the share's directories has a name with Unicode
characters that are unsupported by the NFS
CIFS filenames are Unicode and can contain any character, but
NFS servers and clients must each configure their character
encoding for filenames. The volume cannot import a directory
with any un-mappable characters in its name.
You can use the
command to allow the volume to rename such directories during
import, or you can rename them manually at the filer. Then
restart the import.
Troubleshooting Managed Volumes
" in the
Error show namespace status
appears in the more-verbose
show namespace status
Description/Action
import rename-directories
Correcting Share-Import Errors
output, and one
show namespace
) to see the full error message.
character-encoding
unmapped-unicode
output. Use
.
8-25