You can create a file system and mount it to multiple servers. Then the servers can share this file system. You can create two types of file systems: SFS Capacity-Oriented and SFS Turbo.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
Figure 1 Creating a file system

Parameter | Description | Remarks |
|---|---|---|
AZ | A geographical area with an independent network and an independent power supply. | You are advised to select the AZ where the ECSs reside. |
Protocol Type | SFS supports NFS (NFSv3 only) or CIFS for file system access. NFS is suitable for Linux ECSs, and CIFS is suitable for Windows ECSs. | Select NFS or CIFS based on your need. |
VPC | An ECS cannot access file systems in a different VPC. Select the VPC to which the ECS belongs. NOTE:
| Click View VPC to view existing VPCs or create a new one. |
Auto Capacity Expansion | Specifies whether the capacity of a file system is limited. | If this function is enabled, the capacity of the file system is not limited. Therefore, you do not need to adjust the capacity of the file system. If this function is disabled, you can set the capacity of the file system and resize the file system later as required. NOTE: SFS file systems support resizing if the auto capacity expansion function is disabled. You can only enable the auto capacity expansion function when creating a file system. Once enabled, auto capacity expansion cannot be disabled, and you cannot reconfigure a maximum capacity. Exercise caution when you enable this function. |
Maximum Capacity | The maximum capacity of a single file system needs to be configured when the auto capacity expansion function is disabled. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system. | The value ranges from 1 GB to 512,000 GB. |
Name | User-defined name of the file system. If you create more than one file system, a name suffix is added to each file system name automatically. For example, if you set the name to sfs-name for two new file systems, the two file system names will be sfs-name-001 and sfs-name-002. | The name can contain only letters, digits, underscores (_), and hyphens (-). When creating one file system, enter a maximum of 255 characters. When creating multiple file systems, enter 1 to 251 characters. |
Quantity | Number of file systems to be created | Each cloud account can have a total of 512,000 GB for its file systems. Each cloud account can create a maximum of 20 file systems, one by one or in a batch. |
If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
Figure 2 Creating an SFS Turbo file system

Parameter | Description | Remarks |
|---|---|---|
Region | Mandatory Region of the tenant. Select the region from the drop-down list in the upper left corner of the page. | You are advised to select the region where the servers reside. |
AZ | Mandatory A geographical area with an independent network and an independent power supply. | You are advised to select the AZ where the servers reside. |
Type | Mandatory The following types are supported: Standard, Standard-Enhanced, Performance, Performance-Enhanced, 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, and 250 MB/s/TiB. For more information, see File System Types. | After a file system is created, its type cannot be changed. To change the file system type, you need to create another file system. Plan the file system type in advance. |
Capacity | Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity. The capacity of an SFS Turbo file system cannot be reduced. Set an appropriate file system capacity based on your service needs. | Supported ranges:
|
Bandwidth (GB/s) | Defines the cache bandwidth, which is recommended for workloads with heavy reads and infrequent writes. The higher the bandwidth, the larger the capacity required. |
|
Protocol Type | Mandatory SFS Turbo supports NFS for file system access. | The default value is NFS. |
VPC | Mandatory Select a VPC and a subnet.
NOTE: Upon creation, only one VPC can be added for each file system. Multi-VPC file sharing can be implemented through VPC peering connection. For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide. | - |
Security Group | Mandatory A security group is a virtual firewall that provides network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group. When creating an SFS Turbo file system, you can select only one security group. You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes. The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. After an SFS Turbo file system is created, the system automatically enables the security group port required by the NFS protocol. This ensures that the SFS Turbo file system can be accessed by your servers and prevents file system mounting failures. The inbound ports required by the NFS protocol are ports 111, 2049, 2051, 2052, and 20048. If you need to change the enabled ports, go to the VPC console, choose Access Control > Security Groups, locate the target security group, and change the ports. | - |
Enterprise Project | This parameter is provided for enterprise users. When creating a file system, you can add the file system to an existing enterprise project. An enterprise project is a cloud resource management mode, in which cloud resources and members are centrally managed by project. The default project is default. Select an enterprise project from the drop-down list. | You can select only created enterprise projects. To create an enterprise project, click Enterprise in the upper right corner of the console page. |
Encryption | Optional Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system. If this parameter is selected, the following parameters will be displayed:
| - |
Tag | Optional You can add tags when creating file systems. Tags can help you to identify, classify, and search for your file systems. A tag is composed of a key-value pair.
| - |
Automatic Backup | Cloud Backup and Recovery (CBR) provides backup protection for SFS Turbo and allows you to use backup data to create SFS Turbo file systems. After you configure backup, the system will associate the SFS Turbo file system with the backup vault and apply the selected policy to the vault to periodically back up the file system. The following options are available, among which Do not use is preselected:
| - |
Name | Mandatory User-defined name of the file system. | The name must start with a letter and can contain only letters, digits, underscores (_), and hyphens (-). It must contain at least four characters but no more than 64 characters. |
If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.