Also, the array is a FAS2240 running ONTAP 8.1.4P1.
Thanks! -Phil
On Sun, Jun 29, 2014 at 9:05 AM, Philbert Rupkins <philbertrupkins@gmail.com
wrote:
Hello Toasters,
We inherited an array with vol0's volume language set to undefined. As a result, most of this array's user volumes also do not have vol lang defined. This includes both NFS and CIFS shares. There are currently no problems but we would like to align ourselves with best practices.
Generally speaking, vol lang should be set to eng_us across the environment. A couple questions in regard to making the change from 'undefined' to 'en_us':
- What does a volume language of 'undefined' effectively mean? Does
NetApp default to a language code (POSIX, en_us, other?) when the volume language is set to undefined?
- Can the volume language be safely changed? In the event that files
are inaccessible after changing the volume language, can we simply revert the vol lang setting back to 'undefined' in order to again allow access to the files?
I ask the second question because I see the documentation states that changing the volume language of an existing volume may render some files inaccessible.
Thanks in advance for any insight you have into this matter! Any other suggestions on handling this appropriately would be appreciated!
-Phil