- 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?
Show all
The File System Is Abnormal
Currently, the file system exceptions include deletion error, expansion error, reduction error, and reduction failure. When the file system is in these statuses, refer to the following handling suggestions.
Exception |
Suggestion |
---|---|
Deletion error |
When the file system is in the deletion error status, it can automatically recover to the available state. If the status cannot be restored to available, contact the administrator. |
Expansion error |
When the file system is in the expansion error status, it can automatically recover to the available state. If the status cannot be restored to available, contact the administrator. |
Reduction error |
When the file system is in the reduction error status, it takes approximately five minutes for the file system to restore to the available state. |
Reduction failure |
When the file system is in the reduction failure status, it takes approximately five minutes for the file system to restore to the available state. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.