Hi Kunal,
thanks for the quick answer... appreciated
Just to clarify a bit better.
We are getting some issues running the “volume-size” API command.
We have two different environments –
- Dev – 8.0.1 data ontap Simulator
- Prod – 8.0.2 data ontap
When running the command through the API (version 1.7) into our dev environment, it works fine... But when sending the same command to our prod environment we get the following error “Operation not permitted from vfiler context”.
Which based in the API documentation should be fine:
Given the name of a flexible volume, either return its current size or set the volume's size to the stated amount. | |
Input Name | Range | Type | Description |
new-size | string
optional | Specify the flexible volume's new size using the following format: [+|-]< number > k|m|g|t] If a leading '+' or '-' appears, it indicates that the given flexible volume's size is to be increased or decreased (respectively) by the indicated amount, else the amount is the absolute size to set. The optional trailing 'k', 'm', 'g', and 't' indicates the desired units, namely 'kilobytes', 'megabytes', 'gigabytes', and 'terabytes' (respectively). If the trailing unit character doesn't appear, then < number > is interpreted as the number of kilobytes desired. The file system size of a readonly replica flexible volume, such as a snapmirror destination, is determined from the replica source. In such cases, the value set using "volume-size" is interpreted as an upper limit on the size. A flexible volume that's not a readonly replica which has the "fs_size_fixed" option set may have its size displayed, but not changed. Attempting to set the volume size in this case will result in failure and a EINTERNALERROR error code. Users must be able to adjust readonly replica flexible volume size in order to maintain enough capacity to accommodate transfers from the replica source. Attempting to set a readonly replica destination size to be less than that of its source will result in a failure indicated by the EONTAPI_ENOSPC error code. |
volume | string | The name of the flexible volume for which we want to get or set its size. |
|
Output Name | Range | Type | Description |
is-fixed-size-flex-volume | boolean
optional | Is the flexible volume filesystem size fixed? |
is-readonly-flex-volume | boolean
optional | Is this flexible volume read only? |
is-replica-flex-volume | boolean
optional | Is this flexible volume a replica volume? |
volume-size | string | Either the size we found the given volume to be or the size to which the volume was set (if we're setting its size via the 'new-size' argument above). |
Errno | Description | |
EINTERNALERROR |
EONTAPI_ENOSPC |
Vfiler-enabled |
Yes |
As the command is vfiler-enabled.
I would like to understand if this is the only command that has being changed, or the ones I listed has also changed.
Thanks,
Julio Weber.
