Brian:
I don't know if you used FilerView way back in the day (7mode, 7.x), but it had some really horrible defaults. One of those defaults was the language, the default language was ar.UTF-8 (Arabic). Some folks used the CLI to create our volumes, others used FilerView. If you used FilerView and weren't paying attention, you could easily blow right by that screen and wind up with volumes where the language was set to ar.UTF-8; which we apparently did :-(
Our NetApp SE suggested we use C.UTF-8 as the language for the svms, so that's what we did. New volumes are now created with that as the language. For some of our volume migrations where the data sets/volumes are small, we are using robocopy or rsync. We have a handful of very large volumes with millions of files, rsync/robocopy will choke on those so we have to use snapmirror. snapmirror sets the language on the destination volume to that of the source volume so we wind up with volumes on our new cluster that have a language of ar.UTF-8.
To date, this hasn't been a problem, and I don't think it will be an issue if I were to convert the 7mode volumes to C.UTF-8 before I snapmirror them over. I'm just trying to understand the ramifications of not rebooting the 7mode head after I change the language.
...Darry