Migrating Nfs-Only Directories; Forcing Strict-Attribute Consistency - Acopia Adaptive Resource Switch Cli Maintenance Manual

Troubleshooting Managed Volumes
Removing an Imported Share
This removes the CIFS attributes from NFS-only directories that migrate to the share.
We recommend that you use this feature only under the guidance of Acopia personnel.
bstnA6k(gbl)# namespace insur
bstnA6k(gbl-ns[insur])# volume /claims
bstnA6k(gbl-ns-vol[insur~/claims])# share shr1-next
bstnA6k(gbl-ns-vol-shr[insur~/claims~shr1-next])# no strict-attribute-consistency
bstnA6k(gbl-ns-vol-shr[insur~/claims~shr1-next])# ...
8-16

Migrating NFS-Only Directories

Any file or directory with a back-end FGN is labeled NFS-only; CIFS clients cannot
access it through the volume. It is also impossible to deterministically find the
CIFS-side FGN for an NFS-only directory. This means that the CIFS attributes for
NFS-only directories are inaccessible to the ARX. If the volume cannot find a
directory's CIFS attributes, it cannot make a precise duplicate of the directory. The
migrations for NFS-only directories therefore fail.
You can work around this in one of two ways: rename all NFS-only directories so that
they are accessible through CIFS, or remove an attribute-consistency check at the
destination share. The first option is recommended, but not always possible. The
second option causes an undesirable side-effect; it reduces any undiscovered CIFS
attributes to zero. To remove the attribute-consistency check, go to gbl-ns-vol-shr
mode for the destination share and use the
no strict-attribute-consistency
For example, the following command sequence turns off strict-attribute consistency in
the 'shr1-next' share:

Forcing Strict-Attribute Consistency

Strict-attribute consistency is recommended for most situations. Typically, you restore
this consistency check after the migration is finished. From gbl-ns-vol-shr mode, use
strict-attribute-consistency
strict-attribute-consistency
For example, the following command sequence re-instates strict-attribute consistency
in the 'shr1-next' share:
no strict-attribute-consistency
to enable the consistency checks:
command:
CLI Maintenance Guide