Installation manual

Adding a Managed Volume
Adding a Share
9-32 CLI Storage-Management Guide
Allowing Directory Renames on Import
If the share allows directory renames, the volume renames its colliding directories as
specified by the
modify command (refer back to “Allowing the Volume to Modify on
Import” on page 9-9). From gbl-ns-vol-shr mode, use the
import rename-directories
command to permit the volume to rename this share’s directories:
import rename-directories
This is the default setting.
For example, the following command sequence returns the ‘bills’ share to its default:
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 rename-directories
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...
Renaming Directories with Non-Mappable Characters
(Multi-Protocol)
This section applies to volumes in a multi-protocol (CIFS and NFS) namespace only.
Skip to the next section if the volume supports only CIFS or only NFS.
If directory renames are allowed (as described above), you can set an additional
option for renaming directories with non-mappable characters. (Non-mappable
characters are discussed in the namespace chapter; see “Setting NFS Character
Encoding” on page 7-11.) By default, any directory with a non-mappable character in
its name causes the share import to fail. This default prevents accidental renames. You
can ensure a successful import by allowing the volume to rename the directories. The
volume uses same basic renaming syntax as with any other directory, but replaces
each non-mappable CIFS character with its numeric Unicode equivalent:
new-dirname_share-jobid[-index][.ext]
where new-dirname contains “(U+nnnn)” in place of each non-mappable
character. The nnnn is the Unicode number for the character, shown in
hexadecimal format. The name is truncated if it exceeds 256 characters. For
example, “dir(U+30D2)(U+30AA)_myshare-2.”