Why is the Delete or Unsubscribe button of the file system unclickable?
Please confirm whether a VPC exists under the VPC list of the file system. If so, try to unbind all VPCs of the file system first and then try to delete or unsubscribe after the page is refreshed.
How do I access the file system?
You can access the file system in the following methods:
Within the cloud, you can access the file system through the LAN. The steps are as follows: mount the file system to a cloud server, container or DPS under the same VPC. After successful mounting, you can access the SFS on the cloud server, container or DPS. You can access and use the file system as a common directory and perform read or write operations.
Outside the cloud, you can access the file system by connecting Cloud Dedicated Access (CDA) to the SFS to realize network interoperability between the local data center and the SFS.
Why am I unable to view the shared file directory using showmount-e ip?
Currently, this command is disabled for security reasons. You can view all file systems in the following two ways after logging in:
Method 1: Viewing using the SFS console: Log in to the official website of eSurfing Cloud, click Console, and click SFS Turbo under the Storage module to enter the Console List page.
Method 2: Viewing Using OpenAPI: You can view all file systems by using the interface of Querying Activated File System List of Tenant.
How do I prevent the NFS 4.0 listening port from being considered as a Trojan horse?
Issue Description: After you mount a NAS file system that uses the NFSv4.0 protocol, a random listening port of 0.0.0.0 is listened to. The netstat command cannot identify the process of the listening port. As a result, this port may be considered as a file transfer port subject to the attack of a Trojan horse.
Cause: This random port is listened to by NFSv4.0 clients for callback operations. The default value of the fs.nfs.nfs _ callback _ tcpport kernel parameter is 0. Therefore, the NFSv4.0 clients randomly select a port to listen to, but this random port itself does not cause security risks.
Solution: Before you mount the file system, specify a non-zero deterministic value by configuring the parameter fs.nfs.nfs_callback_tcpport, thus fixing the port for listening. Here is the command:
sudo sysctl fs.nfs.nfs_callback_tcpport=<port>
Replace <port> in the above command for the specific port number you wish to use. By performing the aforementioned operations, you can fix the callback listening port of the NFSv4.0 client, mitigating the occurrence of random ports. This, in turn, decreases the likelihood of misinterpretation as a Trojan horse attack.
What do I do if Chinese characters written to a NAS file system are displayed in garbled text on the client?
Issue Description: In a cross-platform environment, for example, writing Chinese characters (contained in the names or content of files) to an SFS on a Linux or Windows client may cause the characters to be displayed in garbled text on another client.
Cause: By default, Chinese characters are encoded and decoded by using the GBK character set on Linux clients, while being encoded and decoded by using the UTF-8 character set on Linux clients. Before data is written to the SFS, the data is encoded by using the character set that corresponds to the platform. When the data is read on another platform, the data cannot be decoded because the character sets used on these two platforms are incompatible. As a result, Chinese characters are displayed in garbled text.
Solution: We recommend that you use a CIFS protocol to mount an SFS on the Windows client while using an NFS protocol to mount an SFS on the Linux client. This practice avoids platform incompatibility and ensures that Chinese characters can be displayed and decoded normally.
How do I release the handles that are exposed by a client if the SFS cannot terminate processes?
You can use the following tools to release all connections and handles from a CIFS file system
Windows client: use the tcpview tool to remove all connections from a CIFS file system. The procedure is as follows:
1. Download and install the tcpview tool.
2. Launch the tcpview tool.
3. Find the connections related to the CIFS file system in the tool.
4. Right-click the connection and select Close Connection to remove it.
Linux clients: use the killcx tool to remove all connections from a CIFS file system. For details, refer to https://killcx.sourceforge.net/.