I am trying to enable large file support, but when I try to resize the volume it complains that the cluster needs to be 9.12.1 or later. The volume is the source of a snapmirror relationship and both clusters are at 9.12.1P9. Is there something extra I need to do to enable volumes > 100TB?
#Unable to enable large file support
muted ridge
hexed scaffold
Are you setting “-is-large-size-enabled true” ?
muted ridge
yeah, that doc is wrong. 1st off there is no --aggregate option when modifying. 2nd when I run the command I get an error about snapmirror destination needs to be at 9.12.1 or later, but it is.
I opened a case on it.
but thought I would ask here.
::*> vol modify -is-large-size-enabled true -vserver $vserver -volume $volume
Warning: Either the specified volume size or maximum autosize is larger than 100 TB or you are setting is-large-size-enabled flag to true. This will result in
the volume supporting larger size limits. The new limit on the size of the volume will be 300TB. The limit on the size of a file or LUN will be
128TB. If this volume will become the source of a SnapMirror relationship, creation of SnapMirror or FlexCache relationships is only supported with
volumes that reside in clusters with an effective cluster version of 9.12.1 or later, because of incompatible size limits. Revert of the cluster to
an earlier version is not supported when a volume supports larger size limits. All volumes must be 100 TB or less, have all files be 16TB or less,
and have larger size limit support disabled prior to revert.
Do you want to continue? {y|n}: y
Error: command failed: Enabling large volume size on a volume that is the source of a SnapMirror relationship requires the cluster hosting the destination
volume to have an effective cluster version of 9.12.1 or later.
subtle topaz
Just wondering, it’s detecting a mirror. Has the mirror updated since the upgrade? Maybe ONTAP needs a handshake with the destination first?
hexed scaffold
Some thoughts here, btw I am no DP specialist who is what we may need to answer.
Can we break the SM relationship, modify both volumes and then resync from SRC?
Can the DST be modified and then the SRC while still in SM relationship?
muted ridge
I tried that with no luck. There is actually a KB article on this that says the source has to be updated not the dst.
muted ridge
this is what I found out so far. volumes with no snapmirror can be modified. volumes in a SVM-DR can be modified. Volumes with a VSM can not. Support is unfamiliar with this problem and is reaching out to engineering. I am guessing this is yet another bug in 9.12.1p9 😄
muted ridge
Just wondering, it’s detecting a mirror. Has the mirror updated since the upgrad...
yes, upgrade was done 2-3 months prior.
muted ridge
working with support we are still stumped, but I think I may have found a cause. It seems like any volume with the language set to en_US is failing, any with C.UTC-8 work. I am unable to change the language on a volume anymore. Looks like this was removed from the OS. Not sure the reason why.
jovial flare
hmm i did made some changes but from adv or debug
just did some tests :
Error: command failed on vserver "CIFS_SVM" volume "link1": Modification not permitted. Changing the language of a
volume is only supported if the current language is "*.UTF-8" and the new language is "utf8mb4".
as diag you can change but only from UTF-8 based to something else like the only option utf8mb4
i do have utf8mb4 for ex for some tests regarding large char file names ( like emails exports from outlook )
from adv indeed it is stated it is not supported
ex :
AFFA250::*> vol modify -volume link1 -vserver * -language en.UTF-8
Error: command failed on vserver "CIFS_SVM" volume "link1": Changing the language of a volume is not supported.
Contact technical support for assistance.
0 entries were modified.
as a TIP when you see contact support for assistance try with debug 😄
it usually works
jovial flare
i do recommend changing to utf8mb4 if you have odd named files or lagre names more than 250chars
muted ridge
Yeah, well we determined that the language was not the problem. I have yet to figure out how to change the language, but I changed the default language on the vserver and created a new volume. It failed to allow me to enable large file support. So all we know so far is that one SVM is unable to change large file support for volumes in a VSM.
west acorn
VSM = volume snapmirror ?