DetachVscFromFilesystems - Cloud Parallel File Storage - Alibaba Cloud Documentation Center

Unassociates a VSC device from a file system.

Operation description

Only CPFS for Lingjun supports this operation.
Batch execution is supported. In batch execution, only one VscId can be associated with multiple FileSystemIDs, meaning the VscId in the ResourceIds must be the same.

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.

Debug

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.

Operation	Access level	Resource type	Condition key	Associated operation
nas:DetachVscFromFilesystems	update	FileSystem `acs:nas:{#regionId}:{#accountId}:filesystem/{#filesystemId}` Vsc `acs:eflo:{#regionId}:{#accountId}:vsc/{#VscId}`	none	none

Request parameters

Parameter	Type	Required	Description	Example
ResourceIds	array<object>	Yes	The ID information of the file system and virtual storage channel. Each batch can contain up to 10 IDs.
	object	Yes	The ID information of the file system and virtual storage channel. Each batch can contain up to 10 IDs.
FileSystemId	string	No	The ID of the file system.	bmcpfs-290t15yn4uo8lid****
VscId	string	No	The ID of the virtual storage channel.	vsc-8vb864o3ppwfvh****
ClientToken	string	No	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

Parameter	Type	Description	Example
	object
RequestId	string	The ID of the request.	2D69A58F-345C-4FDE-88E4-BF518948****

Examples

Sample success responses

JSONformat

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

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameter	The parameter is invalid.	Illegal parameter.
400	InvalidParameter.FileSystem	Invalid FileSystem in ResourceIds.	The file system in the ResourceIds is invalid.
400	InvalidParameter.ResourceIds	Invalid ResourceIds, can not be empty or batch size large than 10.	ResourceIds parameter error: cannot be empty and the batch size cannot exceed 10.
400	InvalidFilesystemType.NotSupport	This Api does not support this fileSystem type.	The current interface does not support this type of file system.
400	InvalidParameter.VscId	Invalid VscId in ResourceIds.	Invalid VscId in ResourceIds.
400	InvalidParameter.VscIds	Invalid VscId in ResourceIds.VscIds must be the same.	Invalid VscId in ResourceIds. VscIds must be the same.
400	Ram.AddRamParamFailed	Ram check has failed due to param invalid, please check param.	Ram check failed because the parameter is invalid, please check the parameter.
400	FeatureOrAPI.NotSupported	The Feature/API is not supported in this region now.	This feature or API is not currently supported in this region.
403	Forbbiden.Ram	User not authorized to operate on the specified resource, or this API doesn't support RAM.	The user is not authorized to operate the specified resource, or the API does not support RAM.

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