Scalable File Service
Scalable File Service
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- Troubleshooting
-
FAQs
- Concepts
- Specifications
- Restrictions
- Networks
- Billing
-
Others
- How Do I Access a File System from a Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
- What Resources Does SFS Occupy?
- Can a File System Be Accessed Across Multiple AZs?
- How Can I Migrate Data Between SFS and EVS?
- Can I Directly Access SFS from On-premises Devices?
- How Do I Delete .nfs Files?
- How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
- How Do Second- and Third-level Directory Permissions of an SFS Turbo File System Be Inherited?
On this page
Help Center/
Scalable File Service/
API Reference/
SFS Turbo APIs/
Name Management/
Changing the Name of a File System
Changing the Name of a File System
Updated on 2024-11-13 GMT+08:00
Function
This API is used to change the name of an SFS Turbo 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 |
---|---|---|---|
change_name |
Yes |
ShareName object |
SFS Turbo file system to be modified |
Response Parameters
None
Example Requests
Changing the name of an SFS Turbo file system to sfs-turbo-test1
{ "change_name" : { "name" : "sfs-turbo-test1" } }
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
204 |
Request successful |
400 |
Invalid parameter |
409 |
The file system name already exists. |
500 |
Internal error |
Error Codes
See Error Codes.
Parent topic: Name Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.