- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API
- Lifecycle Management
- Connection Management
- Tag Management
- Name Management
- File System Management
-
Storage Interworking Management
- Adding a Backend Target
- Querying Backend Targets
- Obtaining Details About a Backend Target
- Deleting a Backend Target
- Updating the Properties of a Storage Backend
- Updating the Auto Synchronization Policy of a Storage Backend
- Creating an Import or Export Task
- Querying Details About an Import or Export Task
- Listing Import and Export Tasks
- Deleting an Import or Export Task
- Updating a File System
- Directory Management
-
Permissions Management
- Creating a Permission Rule
- Querying Permission Rules of a File System
- Querying a Permission Rule of a File System
- Modifying a Permission Rule
- Deleting a Permissions Rule
- Creating and Binding the LDAP Configuration
- Querying the LDAP Configuration
- Modifying the LDAP Configuration
- Deleting the LDAP Configuration
- Task Management
- Permissions Policies and Supported Actions
- Common Parameters
- Appendix
- SDK Reference
-
FAQs
- SFS Turbo Concepts
- SFS Turbo Specifications
- SFS Turbo Billing
-
SFS Turbo Mount
- What Can I Do If Data of My SFS Turbo File System Is Not the Same When Accessed from Two Client Servers?
- Can I Mount an SFS Turbo File System Across Regions?
- Can I Mount an SFS Turbo File System Across Accounts?
- How Many Cloud Servers Can I Mount an SFS Turbo File System To?
- How Do I Mount a File System to a Linux ECS as a Non-root User
- What Can I Do If Mounting a Subdirectory of a File System Failed?
- SFS Turbo Access
- SFS Turbo Capacity Expansion
- SFS Turbo Deletion
- SFS Turbo Migration
- SFS Turbo Performance
-
Others
- Does the Security Group of a VPC Affect the Use of SFS Turbo?
- What Resources Does SFS Turbo Occupy?
- How Do I Check Whether an SFS Turbo File System Is Available on a Linux Server?
- Can I Upgrade an SFS Turbo File System from the Standard Type to the Performance Type?
- Does SFS Turbo File Systems Support Multi-AZ Deployment?
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- File System Performance Was Poor
- Creating an SFS Turbo File System Failed
- File System Automatically Unmounted
- A Client Server Failed to Access a File System
- Abnormal File System Status
- Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
- Writing to a File System Failed
- Error Message "wrong fs type, bad option" Was Displayed During File System Mounting
- General Reference
Copied.
Creating an Asynchronous Task for a File System
Function
This API is used to create an asynchronous task for a file system. Only tasks for querying directory usage can be created. Such tasks are also referred to as DU tasks. The value of feature in the API request path is dir-usage.
Constraints
This API is only supported for file systems created after August 1, 2023. If there are 10 tasks being executed, no more task can be created. You are advised not to submit five or more requests at a time, or the file system performance may be affected. It takes a long time to query an oversized directory. Do not submit the request repeatedly. The value of feature in the API request path can only be the following:
- dir-usage
This API is only supported for the following types of file systems:
- 20 MB/s/TiB
- 40 MB/s/TiB
- 125 MB/s/TiB
- 250 MB/s/TiB
- 500 MB/s/TiB
- 1,000 MB/s/TiB
For SFS Turbo Standard, Standard-Enhanced, Performance, Performance-Enhanced file systems, use the API for querying the file system directory usage.
URI
POST /v1/{project_id}/sfs-turbo/shares/{share_id}/fs/{feature}/tasks
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID |
share_id |
Yes |
String |
File system ID |
feature |
Yes |
String |
Task type. Only dir-usage is supported currently. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
Account token |
Content-Type |
Yes |
String |
MIME type, which can be application or json |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
path |
Yes |
String |
Valid full path of a directory in the file system. The length of a single-level directory cannot exceed 255 characters, and that of a full path cannot exceed 4,096 characters. |
Response Parameters
Status code: 202
Parameter |
Type |
Description |
---|---|---|
task_id |
String |
Task ID |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
errCode |
String |
Error code |
errMsg |
String |
Error description |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
errCode |
String |
Error code |
errMsg |
String |
Error description |
Example Requests
DU task:
Creating a DU task for querying the usage of a directory. path is used to specify the full path of a valid directory. The length of a single-level directory cannot exceed 255 characters, and that of a full path cannot exceed 4,096 characters.
POST HTTPS://{endpoint}/v1/{project_id}/sfs-turbo/shares/{share_id}/fs/dir-usage/tasks { "path" : "/path" }
Example Responses
Status code: 202
Accepted
{ "task_id" : "d651ea2b-2b20-4c6d-8bbf-2adcec18dac9" }
Status code: 400
Error response
{ "errCode" : "SFS.TURBO.0123", "errMsg" : "feature invalid" }
Status code: 500
Error response
{ "errCode" : "SFS.TURBO.0005", "errMsg" : "internal server error" }
Status Codes
Status Code |
Description |
---|---|
202 |
Accepted |
400 |
Error response |
500 |
Error response |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot