Hi,

I've changed volumes from "C" (POSIX) to en_US.UTF-8 on the fly without any problems, but never to any other language character set.

---- Scott Eno s.eno@me.com

On Jun 29, 2014, at 10:07 AM, Philbert Rupkins philbertrupkins@gmail.com wrote:

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':

1. 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?

2. 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

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

Hey,

default systems locale should be C for all unixoid operating systems if not configured otherwise and since all new volumes inhertig their language setting from the root volume and you specify the root volume language during setup, I’m pretty sure undefined means C.

best,

Alexander Griesser System-Administrator

ANEXIA Internetdienstleistungs GmbH

Telefon: +43-5-0556-320 Telefax: +43-5-0556-500

E-Mail: ag@anexia.atmailto:ag@anexia.at Web: http://www.anexia.athttp://www.anexia.at/

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Philbert Rupkins Gesendet: Sonntag, 29. Juni 2014 18:04 An: Scott Eno Cc: toasters@teaparty.net Betreff: Re: vol lang undefined

Thanks Scott! I think it will be a non-issue for us as well as I cant think of any use case for non-english characters but it's difficult to say with the amount of data contained in these volumes. I'm hoping a value of 'undefined' defaults to en_US so it is a non-issue to make the change.

On Sun, Jun 29, 2014 at 9:40 AM, Scott Eno <s.eno@me.commailto:s.eno@me.com> wrote: Hi,

I've changed volumes from "C" (POSIX) to en_US.UTF-8 on the fly without any problems, but never to any other language character set.

---- Scott Eno s.eno@me.commailto:s.eno@me.com

On Jun 29, 2014, at 10:07 AM, Philbert Rupkins <philbertrupkins@gmail.commailto:philbertrupkins@gmail.com> wrote: 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.commailto: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':

1. 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?

2. 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

_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters