Sun Storage 7000 Unified Storage System: Nfs_stat_to_errno: Bad Nfs Status Return Value: 88

Asset ID:	1-72-1405993.1
Update Date:	2012-06-27
Keywords:

Solution Type Problem Resolution Sure

Solution 1405993.1 : Sun Storage 7000 Unified Storage System: Nfs_stat_to_errno: Bad Nfs Status Return Value: 88

Applies to:

Sun Storage 7410 Unified Storage System - Version Not Applicable and later
Sun Storage 7110 Unified Storage System - Version Not Applicable and later
Sun Storage 7210 Unified Storage System - Version Not Applicable and later
Sun Storage 7310 Unified Storage System - Version Not Applicable and later
Sun ZFS Storage 7120 - Version Not Applicable and later
7000 Appliance OS (Fishworks)

Symptoms

Customer using Red Hat Enterprise Linux clients with NFSv3 may get the below error :

Dec 15 10:23:11 client01 kernel: nfs_stat_to_errno: bad nfs status return value: 88
Dec 15 10:23:11 client01 kernel: nfs_stat_to_errno: bad nfs status return value: 88

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - 7000 Series ZFS Appliances

Cause

The NFSv3 and NFSv2 protocols don't specify the character set.

NFSv4 is supposed to use UTF-8, but not all clients do and this restriction is not enforced by the server. If the UTF-8 only option is disabled for a share, these filenames are written verbatim to the filesystem without any knowledge of their encoding. This means that they can only be interpreted by clients using the same encoding.

Refer to the Link:

Sun ZFS Storage 7000 System Administration Guide - Character Set Encodings

Solution

Use NFSv4 as older version of NFS do not support character encoding.

Back to <Document 1402579.1> Sun Storage 7000 Unified Storage System: How to Troubleshoot NFS Problems.

References

System Admin Guide: Character Set Encodings: http://docs.oracle.com/cd/E22471_01/html/820-4167/shares__shares__protocols.html#shares__shares__protocols___character_set_encodings_

Attachments

This solution has no attachment