Installation manual

Configuring a Namespace
Setting NFS Character Encoding
7-12 CLI Storage-Management Guide
Improper encoding can also present problems during managed-volume import. A file
with a non-mappable CIFS character is imported using its NFS-side name; this may
not have any resemblance to the intended CIFS-side name. A directory with an
non-mappable character can be renamed during import to preserve its resemblance
with the original CIFS-side name. Each share generates an import report containing
the original CIFS-side name and the new name for each renamed file or directory.
From gbl-ns mode, use the
character-encoding nfs command to set the character
encoding for NFS filenames:
character-encoding nfs {iso–8859–1 | utf–8}
where:
iso–8859–1 is ISO 8859–1 (Latin1, single-byte) character encoding, and
utf–8 specifies UTF–8 (Unicode) character encoding.
The default is ISO 8859–1 (Latin1).
For example, this command sequence sets character encoding to “UTF-8” (Unicode)
for NFS filenames in the ‘insur’ multi-protocol namespace:
bstnA6k(gbl)# namespace insur
bstnA6k(gbl-ns[insur])# protocol cifs
bstnA6k(gbl-ns[insur])# protocol nfs3
bstnA6k(gbl-ns[insur])# protocol nfs3tcp
bstnA6k(gbl-ns[insur])# character-encoding nfs utf-8
bstnA6k(gbl-ns[insur])# ...
Presumably, all of the multi-protocol filers behind the ‘insur’ namespace also support
UTF-8 for their NFS filenames.