All Products
Search
Document Center

File Storage NAS:UpgradeFileSystem

Last Updated:Aug 28, 2026

Scales up an Extreme NAS file system or a Cloud Parallel File Storage (CPFS) file system.

Operation description

  • 仅支持极速型 NAS 文件系统和 CPFS 文件系统扩容。

  • 通用型 NAS 按需自动扩容,无须使用本 API。

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

  • Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.

  • API: The API that you can call to perform the action.

  • Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.

  • Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.

    • For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.

    • For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.

  • Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.

  • Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

nas:UpgradeFileSystem

update

*FileSystem

acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}

None None

Request parameters

Parameter

Type

Required

Description

Example

FileSystemId

string

Yes

The ID of the file system.

  • The IDs of Extreme NAS file systems must start with extreme-, for example, extreme-0015****.

  • The IDs of CPFS file systems must start with cpfs-. Example: cpfs-125487****.

extreme-0015****

Capacity

integer

Yes

The new capacity of the file system. The value must be greater than the current capacity. Unit: GiB.

100

DryRun

boolean

No

Specifies whether to perform a dry run. A dry run checks whether the request parameters are valid and the requested resources are available, without actually scaling up the file system or incurring fees.

Valid values:

  • true: performs a dry run. The system checks the required parameters, request syntax, limits, and available NAS resources. If the request passes the dry run, HTTP status code 200 is returned with no value for the FileSystemId parameter. If the request fails, an error message is returned.

  • false (default): performs a dry run and sends the request. If the request passes the dry run, a file system is created.

true

ClientToken

string

No

The client token that ensures the idempotence of the request. You can use the client to generate the token, but the token must be unique across requests.

The token can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How do I ensure the idempotence?

Note

If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.

123e4567-e89b-12d3-a456-42665544****

Response elements

Element

Type

Description

Example

object

RequestId

string

The request ID.

98696EF0-1607-4E9D-B01D-F20930B6****

Examples

Success response

JSON format

{
  "RequestId": "98696EF0-1607-4E9D-B01D-F20930B6****"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.