Table 33 Base-volume and Snapshot-volume Creation Error Codes (continued)
DescriptionHTTP CodeAPI Error
Allocation warning level is higher than the
limit.
400 Bad RequestINV_INPUT_WARN_GT_LIMIT
User space allocation alerts are valid only
with TPVVs.
400 Bad RequestINV_INPUT_USR_ALRT_NON_TPVV
Retention time is greater than expiration
time.
400 Bad RequestINV_INPUT_RETAIN_GT_EXPIRE
Invalid policy specification (for example,
caching or system set to true).
400 Bad RequestINV_INPUT_VV_POLICY
Invalid input: string length exceeds limit.400 Bad RequestINV_INPUT_EXCEEDS_LENGTH
Invalid time specified.400 Bad RequestINV_INPUT_TIME
ID exists.409 ConflictEXISTENT_ID
Modifying a Virtual Volume
To modify or update a volume, use the HTTP PUT method in the URI:
https://<storage system>:8080/api/v1/volumes/<volume name>
where <volume name> is the name of the volume being modified. The message body is a JSON
object with members. Members that can be included in a VV modification request are shown in
Table 34 (page 44).
Table 34 Message Body JSON Objects for Volume Modification Request
DescriptionIgnored ValuesAPI TypeJSON TypeMember
New name of the
volume.
Nonename31stringnewName
(Since WSAPI 1.2)
Comment about the
volume.
Noneprint511stringcomment
(Since WSAPI 1.2)
Time in hours that the
volume would expire.
Zero and negative
values
igint32numberexpirationHours
(Since WSAPI 1.2)
Time in hours that the
volume would be
retained.
Zero and negative
values
igint32numberretentionHours
(Since WSAPI 1.2)
Specify virtual volume
policies.
None except caching
and system, which are
ignored if false.
policies objectobjectpolicies
(Since WSAPI 1.2)
The snap CPG name.Nonename31stringsnapCPG
(Since WSAPI 1.2)
Snap space allocation
warning percent.
Zero and negative
values
igint32numberssSpcAllocWarningPct
(Since WSAPI 1.2)
Snap space allocation
limit percent.
Zero and negative
values
igint32numberssSpcAllocLimitPct
44 Working with Storage Volumes
To Next Page
Loading...
Need help?
General