Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 231 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
CLI Maintenance Guide 8-25
Correcting Share-Import Errors
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 “
Error
” in the
show namespace status
output, and one
of the errors in Table 8-1 appears in the more-verbose
show namespace
output. Use
show namespace
(not
show namespace status
) to see the full error message.
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.
Table 8-1. Share Status Conditions
Status Condition Description/Action
Error: A directory was removed from
the filer during import.
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.
Error: A filename/directory could not
be mapped to the namespace
character encoding.
One of the share’s directories has a name with Unicode
characters that are unsupported by the NFS
character-encoding
.
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
import rename-directories unmapped-unicode
command to allow the volume to rename such directories during
import, or you can rename them manually at the filer. Then
restart the import.