4byte UTF-8 files can be created via NFSv4 which cannot be displayed
Applies to
- ONTAP 9
- UTF-8
- NFSv4
- NFSv3
Issue
- UTF-8 volume allows the creation of 4byte UTF-8 characters when mounted with NFSv4
- This is inconsistent as C.UTF-8 system does not support 4-byte UTF-8 sequences
- This then leads to files that cannot be displayed or folders that cannot be deleted as they are not empty
::> event log show
Time Node Severity Event
------------------- ---------------- ------------- ---------------------------
11/20/2024 22:14:26 node1 ERROR wafl.bagofbits.name: Cannot provide directory entry to NFSv4 client for file ID:417 in volume twice because it contains non-Unicode characters with no NFS alternate name.
- Show volume language
::> vol show -vserver svm1 -volume vol1-fields language vserver volume language
------- ------ --------
svm1 vol1 C.UTF-8
- Linux client language
# echo $LANG
en_US.UTF-8
- After mounting with NFSv4.2 a 4 byte UTF-8 character is created which then cannot be displayed
# unicode=$'uni\xc2\xa2\xf0\x90\x8d\x88d\xe2\x82\xac'
# touch $unicode
# ll
drwxr-xr-x 2 nobody nogroup 4096 Nov 20 22:14 ./ drwxrwxrwx 23 root root 8192 Nov 20 22:14 ../