#NetApp REST limits the flexgroup constituent size to 100GB

1 messages · Page 1 of 1 (latest)

elder cipher
#

I ran a resize of a flexgroup volume (downsize), but encountered errors:

TASK [Resize volume] ***********************************************************
task path: /runner/project/netapp/resize_qtree.yml:61
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NoneType: None
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error resizing volume vol13376: calling: storage/volumes/be81228c-378d-11f1-9fb9-d039ea9b1a54: got {'message': 'Size \"4.35TB\" (\"4784593567744B\") is too small.  Minimum size is \"4.69TB\" (\"5153960755200B\"). ', 'code': '917534'}."}

The volume has 48 constituents, so sounds like it requires 100GB in constituent size. But when I did it with command line, it passed. Volume was resized to 4TB.

Why REST set that limit? Can it be bypassed?

Thanks,
John

split wren
#

100GB is the minimum recommended size for a FlexGroup member. I would suggest you delete and re-create the FlexGroup with fewer members (8 or 16 for example) that way each constituent can be larger