Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • Filename is created with non-utf-8 code on the utf-8 volume, some multi-byte character is showing garbled
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/filename_is_created_with_non-UTF-8_code_on_the_UTF-8_languages_volume
      Applies to ONTAP 9 Issue Create filename from NFS client with non-UTF-8 characters into UTF-8 volume, some characters are showing garbled. Example: Volume language code set as C.UTF-8 Linux clients ac...Applies to ONTAP 9 Issue Create filename from NFS client with non-UTF-8 characters into UTF-8 volume, some characters are showing garbled. Example: Volume language code set as C.UTF-8 Linux clients access via NFSv3 and create a filename using a non-UTF-8 language, such as euc-jp. Check filename by ls command, the file name shows garbled. A file with a file name containing a specific character string cannot be written to the NFS mounted area.
    • Unable to create files using supplementary characters in filename causing NT STATUS 0xc0000033
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_create_files_Error_STATUS_OBJECT_NAME_INVALID_0xc0000033_Why_cant_I_use_supplementary_characters_in_my_filename
      Why can't I use supplementary characters in my filename?
    • Error: cp: /path/file The file access permissions do not allow the specified action
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Error__cp__path_file_The_file_access_permissions_do_not_allow_the_specified_action
      Applies to ONTAP 9 UTF-8 Issue File copy from NFS client to storage volume fails when the file name includes special Korean word '유'. Error: cp: /path/유xx.txt The file access permissions do not allow ...Applies to ONTAP 9 UTF-8 Issue File copy from NFS client to storage volume fails when the file name includes special Korean word '유'. Error: cp: /path/유xx.txt The file access permissions do not allow the specified action
    • What is the Volume and qtree name restriction
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_is_the_Volume_and_qtree_name_restriction
      In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support fo...In addition, using some special characters in qtree names, such as commas and spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. Beginning with ONTAP 9.5, support for 4-byte UTF-8 encoded names enables the creation and display of the file, directory, and tree names that include Unicode supplementary characters outside the Basic Multilingual Plane (BMP). How ONTAP handles multi-byte file, directory, and qtree names
    • Can the volume language be changed after creation in ONTAP?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_the_volume_language_be_changed_after_creation_in_ONTAP
      Note: This is only possible if the current volume language matches *.UTF-8 (such as en_US.UTF-8 or C.UTF-8) and if the new volume language is utf8mb4. Do not change volume language if the volume was e...Note: This is only possible if the current volume language matches *.UTF-8 (such as en_US.UTF-8 or C.UTF-8) and if the new volume language is utf8mb4. Do not change volume language if the volume was ever accessed by NFS clients, otherwise it will corrupt files created using NFS in the past, or files created with NFS are lost.