Sun ZFS Storage 7320
 
Oracle ZFS Storage ZS5-4
 
Oracle ZFS Storage ZS3-2
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7420
 
Oracle ZFS Storage ZS5-2
 
Oracle ZFS Storage ZS4-4
 
Sun ZFS Storage 7120
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-14238865841>

Applies to:

Symptoms

Disk quota exceeded messages on updating a file with extended characters set used in its file name - although there is no quota set.

Cause

The cause appears to be the use of extended character set on NFS share.

SMB/CIFS shares are OK and did not observe any disk quota messages

Solution

This was solved by using the charset code ISO8859-1 on a NFS share exception

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

2.  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 the appropriate section of the ZFS-SA Administration Guide.

References

This solution has no attachment