Sun ZFS Storage 7320
 
Sun Storage 7210 Unified Storage System
 
Sun Storage 7410 Unified Storage System
 
Sun ZFS Storage 7420
 
Sun Storage 7310 Unified Storage System
 
Sun ZFS Storage 7120
 
Sun Storage 7110 Unified Storage System
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 

In this Document

Symptoms

Cause

Solution

Created from <SR 3-7226609071>

Applies to:

Symptoms

Files with non-ASCII characters in their filenames copied via NFS appear to have corrupt filenames.

Example:

  The non-ASCII characters are most commonly found in international names or certain punctuation.

Cause

The ZFS Storage Appliance uses UTF-8 (8-bit Unicode Transformation Format) for directory and file name storage.

By default, the ZFSSA assumes that all file name and directory name data received from NFS clients is already UTF-8 encoded, i.e. using a UTF-8 locale.

In cases where the filenames are encoded with a different method, they will be unreadable in a similar way to the example above.

Solution

1) Use ls or a similar tool to ensure that the client used to copy the files can properly read the filenames. Of course, the client must be able to read the filenames to successfully write them. This step is absolutely critical and commonly missed. Be sure you are specifically checking the data with the extended characters. If the data is not readable, find a client that is using a different encoding method, or work directly from the source where possible.

2) Determine the locale of your client. On Solaris and Linux, use the "locale" command from the shell. If the locale is listed as "C", use ISO8859-1 for the following steps.

Example:

  In this example, since the data is already written in a UTF-8 format, no further configuration or workaround is needed. Assuming this is not the case, proceed to step 3.

3) Navigate to the Shares/Protocols tab. We'll be working with the top section, NFS.

4) Create an NFS exception for the client, and set the "charset" field to match the client encoding. If you have multiple clients with different locales, you may need to repeat this step, while restricting the scope for each set of clients by IP address. If all of your NFS clients use the same encoding, you can skip the exception and define this encoding as the default character encoding at the top of the tab. NFS clients that need to read or write data with non-ASCII filenames will require this setting. Windows clients do not require any configuration.

For detailed instructions on defining NFS exceptions, see this section of the ZFSSA admin guide.

5) Re-migrate the data.

This solution has no attachment