All Products
Search
Document Center

Cloud Parallel File Storage:DeleteFileset

Last Updated:Dec 03, 2025

Deletes a fileset.

Operation description

  • Only Cloud Parallel File Storage (CPFS) V2.2.0 and CPFS for Lingjun V2.7.0 and later support this operation. After you delete a fileset, all data in the fileset is deleted and cannot be restored. Proceed with caution.
  • If deletion protection is enabled for the fileset, you must disable deletion protection before you delete the fileset.
  • After you delete a fileset of CPFS for Lingjun, the storage space is not immediately released and will be recycled within 24 hours. If you want to release storage space immediately, you can clear the data in the fileset and then delete the fileset. Deleted data cannot be restored. Proceed with caution.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
nas:DeleteFilesetdelete
*Fileset
acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
FileSystemIdstringYes

The ID of the file system.

  • The IDs of CPFS file systems must start with cpfs-. Example: cpfs-099394bd928c****.
  • The IDs of CPFS for Lingjun file systems must start with bmcpfs-. Example: bmcpfs-290w65p03ok64ya****.
cpfs-099394bd928c****
FsetIdstringYes

The fileset ID.

fset-1902718ea0ae****
DryRunbooleanNo

Specifies whether to perform a dry run.

During the dry run, the system checks whether the request parameters are valid and whether the requested resources are available. During the dry run, no fileset is deleted.

Valid values:

  • true: performs only a dry run. The system checks the required parameters, request syntax, and service limits. If the request fails the dry run, an error message is returned. If the request passes the dry run, the HTTP status code 200 is returned.
  • false (default): performs a dry run and sends the request. If the request passes the dry run, the fileset is deleted.
false
ClientTokenstringNo

The client token that is used to ensure the idempotence of the request. You can use the client to generate the token, but you must make sure that the token is unique among different 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 parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

2D69A58F-345C-4FDE-88E4-BF518948****

Examples

Sample success responses

JSONformat

{
  "RequestId": "2D69A58F-345C-4FDE-88E4-BF518948****"
}

Error codes

HTTP status codeError codeError messageDescription
400IllegalCharactersThe parameter contains illegal characters.The parameter contains illegal characters.
400MissingFileSystemIdFileSystemId is mandatory for this action.-
400MissingFsetIdFsetId is mandatory for this action.-
400InvalidFilesetId.NotFoundInvalid FilesetId.Fileset does not exist
403OperationDenied.DependencyViolationThe operation is denied due to dependancy violation.-
403OperationDenied.FilesetNotSupportedThe operation is not supported.-
403InvalidOperation.DeletionProtectionThe operation is not allowed due to resource is protected by deletion protection.-
404InvalidFileSystem.NotFoundThe specified file system does not exist.The specified file system does not exist.
404InvalidFsetId.NotFoundThe specified Fileset ID does not exist.-
429Throttling.ApiRequest was denied due to api flow control.The request is throttled.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-10-24The Error code has changedView Change Details
2024-05-31The Error code has changedView Change Details