- 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.
Expanding the Capacity of a File System
Function
This API is used to expand the capacity of a file system.
URI
POST /v1/{project_id}/sfs-turbo/shares/{share_id}/action
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID |
share_id |
Yes |
String |
File system ID |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
Account token |
Content-Type |
Yes |
String |
MIME type |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
extend |
Yes |
Extend object |
Object of extend |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
new_size |
Yes |
Integer |
New capacity of the file system, in GiB For a previous-generation Standard or Performance file system, the capacity ranges from 500 to 32768 (in GiB), and the expansion increment is 100 GiB. For a previous-generation Standard-Enhanced or Performance-Enhanced file system, the capacity ranges from 10240 to 327680 (in GiB), and the expansion increment is 100 GiB. For a 20 MB/s/TiB file system, the capacity ranges from 3686 to 1048576 (in GiB) and must be a multiple of 1.2 TiB. The desired capacity must be converted to GiB and rounded down to the nearest integer. For example, use 4915 GiB for a 4.8 TiB file system and 8601 GiB for a 8.4 TiB file system. The expansion increment is 1.2 TiB. For a 40 MB/s/TiB file system, the capacity ranges from 1228 to 1048576 (in GiB) and must be a multiple of 1.2 TiB. The desired capacity must be converted to GiB and rounded down to the nearest integer. For example, use 4915 GiB for a 4.8 TiB file system and 8601 GiB for a 8.4 TiB file system. The expansion increment is 1.2 TiB. The capacity range and expansion increment of 1,000 MB/s/TiB, 500 MB/s/TiB, 250 MB/s/TiB and 125 MB/s/TiB file systems are the same as those of 40 MB/s/TiB file systems. |
new_bandwidth |
No |
Long |
New bandwidth, in GB. Only HPC Cache file systems support bandwidth change. The following bandwidths are supported: 2G, 4G, 8G, 16G, 24G, 32G and 48G. |
bss_param |
No |
BssInfoExtend object |
Expansion billing details of yearly/monthly resources |
Response Parameters
Status code: 202
Parameter |
Type |
Description |
---|---|---|
id |
String |
ID of the SFS Turbo file system |
name |
String |
Name of the SFS Turbo file system |
Example Requests
Expanding the capacity of a file system to 1,000 GB
{ "extend" : { "new_size" : 1000 } }
Example Responses
Status code: 202
Response body for expanding the capacity of a file system
{ "id" : "67d4bd5e-7b2f-4c24-9a0b-c0038940c6f8", "name" : "sfs-turbo-test" }
Status Codes
Status Code |
Description |
---|---|
202 |
Response body for expanding the capacity of a file system |
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