Writing to a File System Fails

Symptom

Data fails to be written to the file system mounted to ECSs running the same type of OS.

Possible Causes

The ECS security group configuration is incorrect. The port used to communicate with the file system is not enabled.

Fault Diagnosis

Check whether the port of the ECS is enabled and correctly configure the port on the security group console.

Solution

1. Log in to the ECS console.
   1. Log in to the management console.
   2. Click in the upper left corner and select your desired region and project.
   3. Choose Compute > Elastic Cloud Server.

2. On the page displayed, select the target ECS to go to the ECS details page.
3. Click the Security Groups tab and select the target security group. Click Manage Rule to go to the security group console.
4. On the displayed page, click the Inbound Rules tab and click Add Rule. The Add Inbound Rule page is displayed, as shown in Figure 1. Add rules as follows:

   After an SFS Turbo file system is created, the system automatically enables the security group ports required by the NFS protocol. This ensures that the SFS Turbo file system can be successfully mounted to your servers. 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.

   You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes.

   You need to add inbound and outbound rules for the security group of an SFS Capacity-Oriented file system. For details, see Adding a Security Group Rule. For an SFS Capacity-Oriented file system, the inbound ports required by the NFS protocol are ports 111, 2049, 2051, and 2052. The inbound port required by the DNS server is port 53 and that required by the CIFS protocol is port 445.

   Figure 1 Add Inbound Rule
   

5. Click OK. Access the file system again for verification.