Scalable File Service Turbo
Scalable File Service Turbo
- What's New
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- FAQs
-
Troubleshooting
- Mounting a File System Timed Out
- Mounting a File System Failed
- 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
On this page
Show all
What Resources Does SFS Turbo Occupy?
Updated on 2024-11-05 GMT+08:00
To ensure that file systems can be used properly, SFS Turbo occupies the following resources:
- When an SFS Turbo file system is created or expanded, multiple private IP addresses and virtual IP addresses are created in the subnet you specified.
- When an SFS Turbo file system is created, the inbound rules for ports 111, 2049, 2051, 2052, and 20048 are created in the security group you selected. The source IP address defaults to 0.0.0.0/0 in all rules. You can change the IP address as required.
Writing data to a file system consumes the running memory of the server, but does not occupy the server's disk space. The file system uses independent space.
Parent topic: Others
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.