- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- API Documentation
- Troubleshooting
- FAQs
- CFS Service Level Agreement
- Contact Us
- Glossary
- Releases Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- API Documentation
- Troubleshooting
- FAQs
- CFS Service Level Agreement
- Contact Us
- Glossary
Limits and Notes
Limits
Product type | Standard | | High-Performance | | Standard Turbo | | High-Performance Turbo | |
| Specification | Recommended | Specification | Recommended | Specification | Recommended | Specification | Recommended |
Maximum system capacity | 160 TiB | 140 TiB | 32 TiB | 24 TiB | 100 PiB | 4 PiB | 100 PiB | 2 PiB |
Minimum system capacity | None | | None | | 40 TiB | | 20 TiB | |
Maximum system bandwidth | 300 MiB/s | 240 MiB/s | 1 GiB/s | 800 MiB/s | 100 GiB/s | 10 GiB/S | 100 GiB/s | 10 GiB/s |
Maximum number of system files | Min[15,000 x used capacity (GiB), 1 billion] | Min[10,000 x used capacity (GiB), 0.8 billion] | Min[20,000 x used capacity (GiB), 15 billion] | Min[15,000 x used capacity (GiB), 1 billion] | Min[15,000 x deployed capacity (GiB), 1 billion] | Min[10,000 x deployed capacity (GiB), 0.8 billion] | Min[30,000 x deployed capacity (GiB), 1.5 billion] | Min[20,000 x deployed capacity (GiB), 1 billion] |
Maximum number of system directories | 10 million | 8 million | 15 million | 10 million | 10 million | 8 million | 15 million | 10 million |
Maximum length of filename | 255 bytes | 255 bytes | 255 bytes | 255 bytes | 255 bytes | 255 bytes | 255 bytes | 255 bytes |
Maximum length of absolute path | 4096 bytes | 4096 bytes | 4096 bytes | 4096 bytes | 4096 bytes | 4096 bytes | 4096 bytes | 4096 bytes |
Maximum number of directory levels | 1000 | 16 | 1000 | 16 | 1000 | 16 | 1000 | 16 |
Maximum number of files/subdirectories per directory | 1 million | 0.8 million | 1 million | 0.8 million | 1 million | 0.8 million | 1 million | 0.8 million |
Maximum number of concurrently opened files | 65536 | 1000 | 65536 | 1000 | 65536 | 1000 | 65536 | 1000 |
Maximum number of locks per file | 512 | 512 | 512 | 512 | 512 | 512 | 512 | 512 |
Maximum number of clients | 1000 | 100 | 1000 | 100 | 2000 | 1000 | 2000 | 1000 |
Maximum bandwidth per client | 300 MiB/s | 300 MiB/s | 500 MiB/s | 500 MiB/s | 10 GiB/s | 10 GiB/s | 10 GiB/s | 10 GiB/s |
Maximum number of mounted file systems per client | 1000 | 16 | 1000 | 16 | 16 | 8 | 16 | 8 |
Billing | Billed by the actual usage (excluding prepaid) | | Billed by the actual usage (excluding prepaid) | | Billed by the purchased capacity | | Billed by the purchased capacity | |
Supported protocol | NFS/SMB | | NFS | | POSIX/MPI | | | |
Supported OS | Linux/Windows | | | | Linux | | | |
Notes
Turbo series
The Turbo series is mounted using a client. After you run the
mount command on the client installed, you can use the file system the same way as a local file system.The Turbo series is billed according to the capacity purchased. For example, if you purchased a 40 TiB file system of the Turbo storage class, you will be billed at the 40 TiB rates by hour, regardless of how much you actually use. For example, if you use the file system for 1 hour, the fee will be calculated as follows: 40 x 1024 x 0.0857/24/30 = 4.876 USD. The file system can be terminated anytime.
To ensure the cloud load balance of the file system after scaling up, we recommend that you scale up when around 80% of the capacity has been used. Online scale-up is supported and will be imperceptible during the whole process.
The Turbo series cannot be scaled down. You can create a Turbo instance, migrate your data, and then delete the old instance.
Because the self-deployed cluster needs to be set up again, the initial creation of the Turbo series will take about 20 minutes.
It is recommended to mount and use a Turbo file system only on a client in the same availability zone (AZ). Cross-AZ delays may cause issues such as client mount timeouts and disconnections.
If you need the Turbo series with higher specifications (supporting more files, directories, etc.), please submit a ticket.
UID and GID
When the NFS v3.0 protocol is used, if the UID or GID of the file does not exist in the local account, then the UID and GID will be displayed directly. Otherwise, the relevant username and group name will be displayed based on the mapping relationship of the local UID and GID.
When the NFS v4.0 protocol is used, if the Linux version is above 3.0, the UID rules and the GID rules will be the same as those in the NFS v3.0 protocol. Otherwise, the UID and GID of all files will be displayed as
nobody.Note:
When you mount a file system to a client whose Linux version is below 3.0 by using the NFS v4.0 protocol, we recommend that you refrain from performing "change owner" or "change group" on the file or directory. Otherwise, its UID and GID will become
nobody.Supported CIFS/SMB protocols
Supported protocol versions: CIFS/SMB 1.0 and later are supported. However, SMB 1.0 is not recommended for mounting, because it is inferior in terms of performance and features to SMB 2.0 and later and because Windows has stopped its technical support service for Windows versions supporting SMB 1.0 or earlier.
You cannot use NFS and SMB to access the same file system at the same time or directly access an SMB file system via WAN.
Read/write ACL is provided only at the file system level. No ACL is provided at the file/directory level.
IOCTL/FSCTL operations such as sparse files setting, file compression, ENI status query, and reparse point setting are not supported.
Alternate Data Streams are not supported.
Some protocol features in SMB 3.0 or later such as SMB Direct, SMB Multichannel, SMB Directory Leasing, and Persistent File Handle are not supported.
Yes
No
Was this page helpful?