Demonstrating that Vserver Language can be changed in CDOT 8.2 but Volume Language Cannot


Q: Can Vserver language be changed in Clustered Data ONTAP 8.2?
A: Yes!

Q: Can volume language be changed in Clustered Data ONTAP 8.2?
A: No!

After having read two documents which seem to suggest different answers to the above questions (one right* and one wrong), here we demonstrate the answers using the CDOT CLI.

*See the Appendix below for a snippet from the correct official document.

# Verify available aggregate space #

NAC1::> df -A -g

# Create a Vserver with the default language (which is C.UTF-8) and verify the language #

NAC1::> vserver create -vserver vs1 -rootvolume vs1_root -aggregate aggr2_nac1_01 -ns-switch file -rootvolume-security-style ntfs

NAC1::> vserver show -vserver vs1 -fields language
vserver language
------- --------
vs1     C.UTF-8

# Create a Volume inheriting the Vserver default language and verify #

NAC1::> volume create -volume v_test -aggregate aggr2_nac1_01 -size 5g -vserver vs1 -space-guarantee none

NAC1::> volume show -vserver vs1 -volume v_test -fields language
vserver volume language
------- ------ --------
vs1     v_test C.UTF-8

# Change the Vserver language and verify #

NAC1::> vserver modify -vserver vs1 -language en.UTF-8

NAC1::> vserver show -vserver vs1 -fields language
vserver language
------- --------
vs1     en.UTF-8

# Check the test volume’s language and try changing #

NAC1::> volume show -vserver vs1 -volume v_test -fields language
vserver volume language
------- ------ --------
vs1     v_test C.UTF-8

NAC1::> volume modify -volume v_test -?

# The output from the above does not include any options to change the volume’s language. Even if we go into either of the below privilege levels, there is still no option to change volume language #

NAC1::> set -privilege advanced
NAC1::> set -privilege diagnostic

Appendix: The Correct Answer from “Clustered Data ONTAP 8.2 Release Notes”

Support for modifying Vserver's language settings:

Starting with clustered Data ONTAP 8.2, you can modify a Vserver's language and specify the language setting of the volumes in a Vserver. You cannot modify the language of a Vserver with Infinite Volume.

When you create a FlexVol volume without specifying the language, the volume inherits the language from the Vserver it belongs to. After the language of a FlexVol volume is set, you cannot modify it.

When you modify the Vserver's language, it does not modify the language of its volumes.

Comments

  1. What should the VSM and volume language be set to for ESXi, both SAN and NFS?

    What should the VSM and volume language be set to for Windows-only CIFS access?

    What should the VSM and volume language be set to for *nix and Windows CIFS or NFS access?

    ReplyDelete

Post a Comment