Acopia Adaptive Resource Switch, Cli Maintenance Manual

Page: 237 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
CLI Maintenance Guide 8-31
Error: Directory attribute collision
detected during import.
A directory on this share has the same name and path as a
directory on another share, but the attributes are different.
(Directory attributes are permission settings for various users
and groups, along with various other flags.) For example,
suppose share A had a \docs\img directory and share B had a
directory with the same name but different write permissions for
the “Everyone” group.
To allow the volume to modify directory attributes on import,
you can use
modify
on the volume and
import sync-attributes
on
the share. Then retry the import.
Error: Directory collision; Unable to
guarantee strict-attribute-consistency.
(multi-protocol) A directory on this share has the same name and
path as a directory on an already-imported share, but some of the
CIFS attributes are obscured for at least one of them. Obscured
CIFS attributes, due to filer-generated names for the directories,
are common on a multi-protocol filer. The volume requires that
all attributes (for CIFS and NFS) be synchronized for duplicate
directories, and that is impossible under the circumstances.
This can only occur for NFS-only directories, with names that
are illegal in CIFS. If possible, change the directory name(s) so
that they are accessible from CIFS. As an alternative, you can
use
no strict-attribute-consistency
to remove the requirement for
strict-attribute consistency; this reduces all undiscovered CIFS
attributes to zero. You can do this for all shares in the volume,
then restart the import.
Error: Directory name collision
detected during import.
A directory on this share has the same name and path as a file on
an already-imported share. For example, share B has a directory
named /var/log but share A was already imported with a file
named /var/log.
To allow the volume to correct this by changing the directory
name on import, you can use
modify
on the volume and
import
rename-directories
on the share. Alternatively, you can directly
access the filer(s) and correct the problem there. Retry the
import after you address the issue.
Table 8-1. Share Status Conditions (Continued)
Status Condition Description/Action