Linux cannot recognize Korean‑named files that are migrated from EMC to NetApp

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 8

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: nas

Last Updated:

Applies to

ONTAP 9
NFSv4
Data Migration
Rsync

Issue

During data migration from EMC Unity300 to NetApp C30 storage using rsync from a Linux server, files with Korean characters in their names that are created on AIX servers are visible on AIX (NFSv3 mount) but are not visible on Linux servers (NFSv4 mount).

AIX server: This is the NFS client in the production environment(EMC Unity300)
Linux server: This is the data migration server between the EMC Unity300 and the NetApp C30 storage system

Changing the NetApp volume language from C.UTF‑8 to utf8mb4 does not resolve the issue

Packet trace logs show NFSv4 OPEN and LOOKUP requests for problematic filenames returning NFS4ERR_INVAL

Example:
_{32943 2026-02-06 09:53:20.173298 0.035004 xxx.xxx.xxx.62 1000 xxx.xxx.xxx.154 2049 NFS 358 V4 Call (Reply In 32944) OPEN DH: 0x03a6f240/��}
_{32944 2026-02-06 09:53:20.173388 0.000090 xxx.xxx.xxx.154 2049 xxx.xxx.xxx.62 1000 NFS 166 V4 Reply (Call In 32943) OPEN Status: NFS4ERR_INVAL}_{32946 2026-02-06 09:53:20.173581 0.000108 xxx.xxx.xxx.62 1000 xxx.xxx.xxx.154 2049 NFS 358 V4 Call (Reply In 32947) OPEN DH: 0x03a6f240/��}
_{32947 2026-02-06 09:53:20.173584 0.000003 xxx.xxx.xxx.154 2049 xxx.xxx.xxx.62 1000 NFS 166 V4 Reply (Call In 32946) OPEN Status: NFS4ERR_INVAL}
_{32948 2026-02-06 09:53:20.173707 0.000123 xxx.xxx.xxx.62 1000 xxx.xxx.xxx.154 2049 NFS 270 V4 Call (Reply In 32950) LOOKUP DH: 0x03a6f240/��}
_{32950 2026-02-06 09:53:20.173710 0.000001 xxx.xxx.xxx.154 2049 xxx.xxx.xxx.62 1000 NFS 166 V4 Reply (Call In 32948) LOOKUP Status: NFS4ERR_INVAL}