Hello Milazzo

Have a look at the "File Access and Protocols Management Guide" -> "File Sharing Between NFS and CIFS"

The whole chapter is (imho) important to your subject.

"Sometimes, you‘ll need special NFS <-> CIFS (UTF-16) translationtables. For more information, see the na_charmap(1) man page. This functionality supports the CATIA® MCAD and Mathematica® applications as well as other applications that have this requirement."

charmap [volname [mapspec]]

There also is a nice freeware utitlity named „detox“. Detox is a utility designed to clean up filenames. It replaces difficult to work with characters, such as spaces, with standard equivalents. It will also clean up filenames with UTF-8 or Latin-1 (or CP-1252) characters in them. http://detox.sourceforge.net/

The effect of the VOLLANG is:

1) Newer CIFS Clients will always use UTF-16 2) NFS Clients will see either see/use UTF-8 (if you append ".UTF-8" to VOLLANG) or ISO-8859-XX (if you don't append ".UTF-8" ), or ... See below ... 3) "Dumb" OEM-Clients like very old Windows-Versions will use the subset defined by the VOLLANG: C => ASCII de => CP850 en => CP850 en_US => CP437

To predict the behaviour use: priv set -q advanced ; registry walk etc.lang

etc.lang.codepage.C=ascii <- "Dumb" clients etc.lang.charset.C=iso-8859-1 <- NFS clients etc.lang.description.C=POSIX <- Full name description ... etc.lang.codepage.en=cp850 etc.lang.charset.en=iso-8859-1 etc.lang.description.en=English ... etc.lang.codepage.en_US=cp437 etc.lang.charset.en_US=iso-8859-1 etc.lang.description.en_US=English (US)

or after setting the VOLLANG and using: priv set -q advanced ; vol lang VOLNAME

you'll see

Volume language is de.UTF-8 (German with UTF-8) Translation Versions OEM Character set is cp850|cp850|Fri Oct 2 00:00:53 MEST 1998 NFS Character set is utf-8|utf-8|Fri Oct 2 00:00:53 MEST 1998

Volume language is de (German) Translation Versions OEM Character set is cp850|cp850|Fri Oct 2 00:00:53 MEST 1998 NFS Character set is iso-8859-1|iso-8859-1|Fri Oct 2 00:00:53 MEST 1998

I'm from Germany... ;-)

WARNING! If you switch between "LANG" and "LANG.UTF-8" - or vice versa - the filer will offer you to "halt the system"... to start a filesystem check to detect files with "bad names" ...

I'ld prefer "detox" instead and "charmap" to correct specific details.

Best regards Dirk

Hi all

I need to append the .UTF-8 to the language code of some volume with a mixed security.

I need to know if this can change or alter the name of the files there contained, accessing them both from NFS and CIFS.

This because using Enterprise Vault SP2 on a NetApp share and placeholder (policy ad hoc for ev) the size of archived files reports “0” bytes instead of the real value reflecting the original data…

My EV is 7.5 SP2 but I’ve only found a doc related to EV v.6 SP2 (http://seer.entsupport.symantec.com/docs/282785.htm) and I put here an extract of the readme attached to EV installation:

Anyway supposing that they’re right, can I add this UTF-8 and be sure?

Thanks a lot

*NetApp Filer placeholder shortcuts appear to be 0 KB **[Ref E1029910, E1017992, DOR1006]***

Placeholder shortcuts created on NetApp Filers fail to reflect the original file size, appearing instead to be 0 KB, if either of the following conditions applies:

* The language setting on the NetApp Filer is *Shift JIS* (Japanese)
* The language setting on the NetApp Filer is not appended with
  *.UTF-8*, and the name of the file that is converted to a
  placeholder contains Unicode characters.

To avoid the second condition, you can append *.UTF-8* to the language setting on the NetApp Filer. To do this, enter the following command from the NetApp Filer's administration console:

vol lang /volume_name language_code/.UTF-8

where /volume_name/ specifies the volume, and /language_code/ is the code for the language setting.

For example:

vol lang vol0 en.UTF-8

*Note*: You can view a list of the language settings the NetApp Filer supports by entering the following command:

vol lang