Installation manual

Adding a Managed Volume
Adding a Share
CLI Storage-Management Guide 9-31
bstnA6k(gbl-ns-vol[wwmed~/acct])# share bills
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# no import sync-attributes
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...
Preventing Directory Renames During Import
Whether or not the managed volume is allowed to synchronize attributes on this
share, it has occasion to rename any directories that collide with previously-imported
files. Attribute synchronization is not enough to resolve a naming conflict between a
directory and a file. The renamed directory follows the same convention described
earlier; recall “Allowing the Volume to Modify on Import” on page 9-9.
Each share generates a report while it imports, and this report includes the original
name and the new name for each renamed directory.
You can use the
no import rename-directories command to protect this share against
any directory renames.
no import rename-directories
If you set this, a directory/file conflict causes the share to fail its import, and a
directory/directory conflict fails the import unless the volume is allowed to
synchronize the attributes of the directories (as shown above). The CLI Maintenance
Guide explains how to remove a share from a namespace if its import fails; after that,
you can directly connect to the back-end share and repair the directories that collided
(change names, reset attributes, and so forth).
For example, the following command sequence prevents the volume from renaming
any colliding directories in the ‘bills’ share during an import:
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])# no import rename-directories
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...