![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1633644.1 : Sun ZFS Storage Appliance: Appliance does not Convert the Path Name Codeset in a DNS-less Configuration
When you are using NFS encoding on ZFS Storage Appliance, inappropriate DNS settings cause NFS not being able to convert the path names into the expected encoding. In this Document
Created from <SR 3-8244262131> Applies to:Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases] Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases] Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases] Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases] 7000 Appliance OS (Fishworks) SymptomsAs a part of NFS service functionality, users can set encoding to specify what character code set the path names are using. However, in a DNS-less environment, the NFS code fails to call the conversion code and may result in garbled path names.
CauseIn mountd.c and nfs_cmd.c code, there are places we are calling DNS lookup. The call to DNS lookup has now been changed so that it works even if a DNS server is not present. SolutionUpgrade to Appliance Firmware Release 2013.1.1.5 or later. References<BUG:17969958> - SHARE_NFS(1M) 'CHARSET' OPTION DOES NOT WORK IN DNS-LESS ENVIRONMENT<BUG:18130201> - ADD CP932 AND SHIFT_JIS ENTRIES TO NFS CHARACTER ENCODING DROP-DOWN LIST <BUG:17786265> - SUPPORT FOR CP932 AND SHIFT_JIS JAPANESE CHARACTER ENCODINGS IN NFS Attachments This solution has no attachment |
||||||||||||||||||
|