Reviewed-by: gtema <artem.goncharov@gmail.com> Co-authored-by: Wei, Hongmin <weihongmin1@huawei.com> Co-committed-by: Wei, Hongmin <weihongmin1@huawei.com>
16 KiB
Mounting an NFS File System to ECSs (Windows)
After creating a file system, you need to mount the file system to ECSs so that they can share the file system.
This section uses Windows Server 2012 as an example to describe how to mount an NFS file system. For other versions, perform the steps based on the actual situation.
Operations on BMSs and containers (CCE) are the same as those on ECSs.
Prerequisites
- You have created a file system and have obtained the mount point of the file system.
- At least one ECS that belongs to the same VPC as the file system exists.
- The IP address of the DNS server for resolving the domain names of the file systems has been configured on the ECS. For details, see Configuring DNS. SFS Turbo file systems do not require domain name resolution.
Limitations and Constraints
Procedure
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Under Computing, click Elastic Cloud Server to switch to the ECS console.
- Go to the ECS console and log in to the ECS running Windows Server 2012.
- Install the NFS client.
- Click Server Manager in the lower left corner. The Server Manager window is displayed, as shown in Figure 1.
- Click Add Roles and Features. See Figure 2.
- Click Next as prompted. On the Server Roles page, select Server for NFS, as shown in Figure 3.
- Click Next. In the Features page, select Client for NFS and click Next, as shown in Figure 4. Confirm the settings and then click Install. If you install the NFS client for the first time, after the installation is complete, restart the client and log in to the ECS again as prompted.
- Modify the NFS transfer protocol.
- Check that the IP address of the DNS server for resolving the domain names of the file systems has been configured on the ECS before mounting the file system. For details, see Configuring DNS. SFS Turbo file systems do not require domain name resolution.
- Run the following command in the Command Prompt of the Windows Server 2012 (X is the drive letter of the free disk). Select the ECS that belongs to the same VPC as the file system to mount the file system.
For SFS Capacity-Oriented file systems: mount -o nolock mount point X:
For SFS Turbo file systems: mount -o nolock -o casesensitive=yes IP address:/! X:
- Free drive letter of the disk: A drive letter that is not in use, such as driver letter E or X.
- The mount point of an SFS Turbo file system is the root directory. Ensure that an English exclamation mark (!) is added to the mount point, for example, 127.0.0.1:/!.
- casesensitive=yes indicates that file names are case sensitive during file search. If this parameter is not added, the performance of creating files in a large directory will deteriorate.
You can move the cursor to the mount point and click
next to the mount point to copy the mount point. For details, see Figure 8. If the information shown in Figure 9 is displayed, the mounting is successful.
- After the file system is mounted successfully, you can view the mounted file system on the This PC window, as shown in Figure 10.
If the mounting fails or times out, rectify the fault by referring to Troubleshooting.
Troubleshooting
If a file system is mounted to a Linux ECS and a Windows ECS, you cannot write data to the files created by the Linux ECS on the Windows ECS. To address this problem, you need to modify the registry and change both values of UID and GID of the Windows user accessing NFS to 0. This section uses Windows Server 2012 as an example. Do as follows:
- Choose Start > Run and enter regedit to open the registry.
- Enter the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default directory. See Figure 11.
- Right-click the blank area and choose New > DWORD Value from the shortcut menu. Set AnonymousUid and AnonymousGid to 0. Figure 12 shows a successful operation.
- After modifying the registry, restart the server for the modification to take effect.