We are running in to a problem when copying files to a CIFS share running on CDOT 9.4. All files that contains 'special' characters in the file name is rejected. We need to store forensics dumps of cell phone data with emojis and other off the wall characters. As these are evidence, we cannot alter the files to comply with the base UTF character set that NetApp uses
The email alert (see below) that gets generated has some steps to enable UTF surrogate pairs, but the syntax isn't valid (as far as I can tell) for CDOT 9.4. So, I have two/three questions:
1. What is the ramification of enabling UTF surrogate pairs (should we do it)?
2. What is the proper syntax to implement the change?
2.a. How do we make the change persistent across reboots?
Subject: NODE_2: wafl.dir.surrpair.filename [LOG_ERR]
Filer: NODE_2
Time: Fri, Sep 20 09:50:41 2019 -0400
Severity: LOG_ERR
Message: wafl.dir.surrpair.filename: Failed to create a file with surrogate pair characters in the name in the directory /vol/<redacted>.
Description: This message occurs as a warning when a file name with surrogate pair characters in UTF-16 encoding fails to be created in a parent directory.
Action: To allow names with surrogate pairs to be created, use the following
command: "setflag wafl_reject_surrogate_pair 0". If the option needs to be set across reboots, set the bootarg 'wafl-accept-surrogate-pair?' to "true" at the LOADER prompt.
Source: wafl_exempt00
Index: 14321181
