Acopia Adaptive Resource Switch, Руководство по обслуживанию CLI

Страница: 236 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
8-30 CLI Maintenance Guide
Error: Detected
collisions/inconsistencies during no
modify import.
Two or more of the volume’s shares had common filenames that
either
collided or had NFS/CIFS naming inconsistencies , and
this volume disallows import if it encounters either of these
problems. As an example of a collision, suppose share A and
share B had the same file in the same path, \docs\index.htm:
these files would collide. A naming inconsistency can only
occur for a directory in a multi-protocol (NFS and CIFS)
namespace; the CIFS-side directory name has unicode
characters that are inexpressible on the NFS-side (see the
documentation for the
character-encoding
command). The
volume must be allowed to modify the directory (or one of the
colliding files) for the import to succeed: the directory or file
must be renamed.
All duplicate files and naming inconsistencies are recorded in
the import reports for each share. These reports are named
“import.
job-id . share-name . share-id .rpt.” Use
show reports
to
list all import reports and read their contents.
Using the import report for each share, resolve all file collisions
and naming inconsistencies before re-importing. Go to the filers
and rename the files, move them, and/or resolve that certain file
renames are acceptable. Once the issues are cleared, use the
gbl-ns-vol
reimport-modify
and
modify
commands to allow
modification (renames) on import. To rename inconsistent
NFS/CIFS directories, use the
import rename-directories
unmapped-unicode
command, too. Then re-import the volume’s
shares.
Error: Device Offline
The share’s back-end filer went offline for an extended time in
the middle of the import. You can remove the share from the
volume, or resolve the issue at the filer and retry the import.
Depending on when the filer went offline, you may need to use
remove-share migrate
or
remove-share nomigrate
to remove the
share, instead of a simple
no share
command.
Table 8-1. Share Status Conditions (Continued)
Status Condition Description/Action