Installation manual

Adding a Managed Volume

Adding a Share

9-30 CLI Storage-Management Guide

choose an alternative: instead of renaming the directory, synchronize its attributes

with that of its already-imported counterpart. The volume presents the two directories

as a single directory, with the aggregated contents of both and the attributes of the one

that was imported first.

For a directory that collides with an already-imported file, a rename is the only

possible method for resolving the conflict.

From gbl-ns-vol-shr mode, use the

import sync-attributes command to allow

directory-attribute synchronization for the current share.

import sync-attributes

For example, the following command sequence allows the /acct volume to

synchronize directory attributes (instead of renaming conflicting directories) in the

‘bills’ share.

bstnA6k(gbl)# namespace wwmed

bstnA6k(gbl-ns[wwmed])# volume /acct

bstnA6k(gbl-ns-vol[wwmed~/acct])# share bills

bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# import sync-attributes

bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...

Disabling Directory-Attribute Synchronization on Import

By default, if two shares have matching directories but conflicting attributes, the

directories collide. Like a file collision, this is handled by renaming the directory as

specified by the

modify flag. Use the no import sync-attributes command to disable the

synchronization:

no import sync-attributes

For example, the following command sequence turns off attribute synchronization in

the ‘bills’ share during an import:

bstnA6k(gbl)# namespace wwmed

bstnA6k(gbl-ns[wwmed])# volume /acct

For heterogeneous multi-protocol namespaces, always enable synchronization with the

import sync-attributes command. A multi-protocol volume compares both CIFS and NFS

attributes, thereby dramatically increasing the likelihood of directory collisions and

renames.