Will data be unavailable while converting unicode to UTF-8 with NFSv4 enablement?
Applies to
- ONTAP 9
- NFS
Answer
There is no disruption associated.
Additional Information
- How do the CREATE_UCODE and CONVERT_UCODE options control unicode conversion in Data ONTAP releases?
- After the conversion what will 'language' for each volume show? Will it be C.UTF8 or utf8mb4?
- it will show Language: C.UTF-8
- What about files that might be Cyrillic language or other non English variants?
- When it is converted, Cyrillic and will generally be limited to the code units available to C.UTF-8, but if those characters look normal already then they shouldn't look any different.
- Anything the looks incorrect now will remain on NFSv4 until you ALSO change to utf8mb4 and remount. This will handle those odd characters.
- Anything that is stored in the bag of bits should show up prepended with || filenames, and need to be renamed by a CIFS/NFSv3 client.
- Can the volume language be changed after creation in ONTAP?
- Implications of changing the language of a volume after data has been written to it?
- Filename is created with non-utf-8 code on the utf-8 volume, some multi-byte character is showing garbled