In 5.3 releases, Unicode is automatically enabled. All directories must be in unicode format to be accessed from windows clients. Conversion occurs the first time the directory is accessed from WIndows.

If your filer is used by NFS only, then unicode is not used.

If your filer is CIFS only, or is used in a multiprotocol environment, all directories accessed by cifs are in unicode format. The language setting indicates what PC character set to use to translate to/from unicode for requests from CIFS that do not contain unicode file names. It is also used to translate unicode file names to a character set supported by nfs. The language setting for a volume also indicates the character set used by nfs clients. So you should set the language to the one that represents the PC character set and the nfs character set used by the majority of your clients.

If you have clients that require different pc character sets, or different NFS character sets, then you should assign them to different volumes and set the language on those volumes appropriately.

The filer dump/restore utilities understand unicode and will preserve unicode and non-unicode file names. NT utilities for backup/restore also preserve unicode names.

The filer allows file names with a maximum of 255 unicode characters, and a maximum path length of 1024 characters. Non-unicode file names received from NFS are also limited to 255 bytes.

Joan Pearson Network Appliance At 11:39 AM 1/31/00 , you wrote:

Hi,

Sorry 'bout the bunch more questions below - I'd like to understand what this means in more detail if there's knowledgable folks out there.

Is unicode mode enabled automatically on the wafl fs? Is the language setting relevant in a CIFS only environment or is it only to allow translation between single-byte clients and wide charsets? If setting the language is needed what impact does this have with multiple language clients, ie one kanji, one US English and maybe a laptop user from Korea? Does it have any impact if the user consistently uses the same language/nt build on the client? How about backup/restore via CIFS - are we OK as long as the CIFS backup client understands unicode? Any idea on maximum filename lengths? The Win32 SDK says 32,000 unicode characters if prefixed with "\?" - anyone stress tested this?

Hope I get it with answers to all these questions - talk about opening pandoras box Andrew ;-)

TIA, Alan

----- Original Message ----- From: Joan Pearson jpearson@netapp.com To: Andrew-M.Webster@db.com Cc: toasters@mathworks.com Sent: Monday, January 31, 2000 5:11 PM Subject: Re: Toasters in Compaq Racks and Unicode Files

...

Hi, Some requests from NT do not supply Unicode file names, but instead use the PC character set. Setting the language indicates which PC character set is in use, so that it can be properly translated to Unicode.

The volume's language should be set as soon as possible after bringing up a 5.3 release.

Joan Pearson Network Appliance

At 10:47 PM 1/30/00 , you wrote:

...

Hi There,

Has anyone out there installed F 760es in Compaq racks? Any special

tips,

...

...

problems etc....

Also, can anyone relay any experiences (good or bad) with using

Non-English

...

...

files and directories for CIFS clients on Toasters.

And finally, the System. Admin Guide talks about setting a language of a volume with the "vol lang volume langcode" command. Does this having any affect for Unicode clients, ie NT?

Any help appreciated.

-- Andrew Webster Windows NT Consultant Sanno Move Project Deutsche Securities Ltd. - Tokyo Tel. +81-3-5408-4787 Fax. +81-3-5401-6998 Andrew-M.Webster@db.com