invalide size of new constituent of a flexgroup

[grocanar]

Hi

when i want to add a new constituent of a flexgroup this constituent didn't take the same size of othe constituent.

 cns_svm_ng BigRawdataCNS__0001 11.87TB
cns_svm_ng BigRawdataCNS__0002 11.94TB
cns_svm_ng BigRawdataCNS__0003 11.82TB
cns_svm_ng BigRawdataCNS__0004 11.91TB
cns_svm_ng BigRawdataCNS__0005 11.80TB
cns_svm_ng BigRawdataCNS__0006 9.54TB
cns_svm_ng BigRawdataCNS__0007 8.97TB
cns_svm_ng BigRawdataCNS__0008 8.15TB
cns_svm_ng BigRawdataCNS__0009 8.19TB
9 entries were displayed.

THat s a bit annoying as the size is decreasing. 

how can i prevent this size to decrease when i m adding new constituent 

[keitha]

The default behaviour of FlexGroups is to add new memebers the same size as the existing member volumes. However, what I suspect is happening here is space is being balanced from from volumes with lots of space to volumes that are nearing full. FlexGroup will attempt to keep files that live in the same directory together if possible to optimize for performance. In this case, I suspect you have more new files in existing directories than new directories which is causing writes to go to existing volumes, thus making ONTAP "Flex" the space by shrinking the new empty volumes and growing the existing volumes.

No harm but curious why you wanted the new volumes to be the same size?

[grocanar]

Well i would like to have the same size because of the limitation of file size. 
I would prefer to have a lilmitation that won't change because of the location of specific constituent 

[ChinaLongRen]

thin volume ?   use think volume

[grocanar]

I can't .
i have surallocation on my aggregates 

[ChinaLongRen]

Since writing files to the component volume is not balanced, thin volume it will be automatically adjusted according to the file capacity inside, which is reflected in the later stage