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
Show all
Help Center/
Scalable File Service/
API Reference/
Common Parameters/
SFS Turbo File System Statuses
SFS Turbo File System Statuses
Updated on 2022-09-16 GMT+08:00
- SFS Turbo file system status elements
Returned Value
Description
100
CREATING: The file system is being created.
200
ACTIVE: The file system is active. An SFS Turbo file system can be mounted in this status.
300
FAILED: The job failed.
303
CREATE_FAILED: The cluster failed to be created.
400
DELETED: The cluster has been deleted.
800
FROZEN: The cluster has been frozen.
Parent topic: Common Parameters
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.
