| Item | Maximum number |
|---|---|
| Number of file controllers | 16 |
| Item | Maximum specification | Notes |
|---|---|---|
| Number of file systems | 16*n/(n+1), the result is rounded down n is the number of file controllers |
The actual number of file systems that can be created is determined by the capacity of the file system and the number of disk slots that are currently free. See the explanation below the table for details. |
| Capacity of a single file system | 1 PiB | |
| Number of files in a single file system | 1 billion | - |
| Size of a single file in the file system | 4 TiB | - |
Note:
Since file systems occupy disk slots of file controllers, and the number of slots occupied is related to the capacity of the file system, the actual number of file systems that can be created is determined by the capacity of the file system and the number of disk slots that are currently free. The specific explanation is as follows:
Each file controller can provide 32 disk slots. A file storage cluster can provide a total of 32*n slots, where n is the number of file controllers.
The relationship between the number of disk slots required for a single file system (required_slot), the file system capacity (capacity), and the number of file controllers (n) is:
- When n ≤ capacity / 32 TiB, required_slot = (⌈ capacity / 32 TiB ⌉ + 1) * 2, where "⌈⌉" represents rounding up.
- When n > capacity / 32 TiB, required_slot = (n + 1) * 2.
When the number of free disk slots in the file storage cluster is insufficient, it is not possible to create new file systems. You will see the prompt
Invalid storage capacity for the file system.. In this case, deploy another file storage cluster and create the required file systems.
