From 8deffc479b5cc771d2b6ebf897e76e15bcfcd818 Mon Sep 17 00:00:00 2001 From: zhangyue Date: Tue, 8 Aug 2023 07:48:04 +0000 Subject: [PATCH] SFS UMN DOC Reviewed-by: Muller, Martin Co-authored-by: zhangyue Co-committed-by: zhangyue --- docs/sfs/umn/ALL_META.TXT.json | 10 +- docs/sfs/umn/CLASS.TXT.json | 10 +- .../sfs/umn/en-us_topic_0000001476461694.html | 76 ++++++++ .../sfs/umn/en-us_topic_0000001515917172.html | 37 ---- .../sfs/umn/en-us_topic_0000001515917216.html | 19 -- .../sfs/umn/en-us_topic_0000001527141597.html | 19 ++ .../sfs/umn/en-us_topic_0000001567076569.html | 76 -------- .../sfs/umn/en-us_topic_0000001567076661.html | 167 ------------------ docs/sfs/umn/en-us_topic_0034428728.html | 167 ++++++++++++++++++ docs/sfs/umn/en-us_topic_0037934210.html | 37 ++++ docs/sfs/umn/sfs_01_0007.html | 2 +- docs/sfs/umn/sfs_01_0024.html | 2 +- docs/sfs/umn/sfs_01_0025.html | 4 +- docs/sfs/umn/sfs_01_0034.html | 4 +- docs/sfs/umn/sfs_01_0043.html | 4 +- docs/sfs/umn/sfs_01_0052.html | 2 +- docs/sfs/umn/sfs_01_0053.html | 2 +- docs/sfs/umn/sfs_01_0054.html | 2 +- docs/sfs/umn/sfs_01_0055.html | 2 +- docs/sfs/umn/sfs_01_0056.html | 2 +- docs/sfs/umn/sfs_01_0104.html | 8 +- 21 files changed, 329 insertions(+), 323 deletions(-) create mode 100644 docs/sfs/umn/en-us_topic_0000001476461694.html delete mode 100644 docs/sfs/umn/en-us_topic_0000001515917172.html delete mode 100644 docs/sfs/umn/en-us_topic_0000001515917216.html create mode 100644 docs/sfs/umn/en-us_topic_0000001527141597.html delete mode 100644 docs/sfs/umn/en-us_topic_0000001567076569.html delete mode 100644 docs/sfs/umn/en-us_topic_0000001567076661.html create mode 100644 docs/sfs/umn/en-us_topic_0034428728.html create mode 100644 docs/sfs/umn/en-us_topic_0037934210.html diff --git a/docs/sfs/umn/ALL_META.TXT.json b/docs/sfs/umn/ALL_META.TXT.json index a4815d186..5702d1c35 100644 --- a/docs/sfs/umn/ALL_META.TXT.json +++ b/docs/sfs/umn/ALL_META.TXT.json @@ -160,7 +160,7 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001567076661.html", + "uri":"en-us_topic_0034428728.html", "product_code":"sfs", "code":"17", "des":"After creating a file system, you need to mount the file system to servers so that they can share the file system.In this section, ECSs are used as example servers. Opera", @@ -260,7 +260,7 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001567076569.html", + "uri":"en-us_topic_0000001476461694.html", "product_code":"sfs", "code":"27", "des":"You can search for file systems by file system name keyword or file system status, and view their basic information.In the upper right corner of the page, click Search by", @@ -270,7 +270,7 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001515917216.html", + "uri":"en-us_topic_0000001527141597.html", "product_code":"sfs", "code":"28", "des":"Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.The file sys", @@ -460,7 +460,7 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001515917172.html", + "uri":"en-us_topic_0037934210.html", "product_code":"sfs", "code":"47", "des":"When a file system is mounted to servers using the mount command, message timed out is displayed.Cause 1: The network status is not stable.Cause 2: The network connection", @@ -633,7 +633,7 @@ "uri":"sfs_01_0072.html", "product_code":"sfs", "code":"64", - "des":"SFS Capacity-Oriented supports standard NFSv3. SFS Turbo supports the standard NFSv3 protocol.SFS Capacity-Oriented and SFS Turbo all support the standard NFSv3 protocol.", + "des":"SFS Capacity-Oriented and SFS Turbo all support the standard NFSv3 protocol.", "doc_type":"usermanual", "kw":"What Access Protocols Are Supported by SFS?,Specifications,User Guide", "title":"What Access Protocols Are Supported by SFS?", diff --git a/docs/sfs/umn/CLASS.TXT.json b/docs/sfs/umn/CLASS.TXT.json index d2f1272ce..430ced313 100644 --- a/docs/sfs/umn/CLASS.TXT.json +++ b/docs/sfs/umn/CLASS.TXT.json @@ -147,7 +147,7 @@ "desc":"After creating a file system, you need to mount the file system to servers so that they can share the file system.In this section, ECSs are used as example servers. Opera", "product_code":"sfs", "title":"Mounting an NFS File System to ECSs (Linux)", - "uri":"en-us_topic_0000001567076661.html", + "uri":"en-us_topic_0034428728.html", "doc_type":"usermanual", "p_code":"16", "code":"17" @@ -237,7 +237,7 @@ "desc":"You can search for file systems by file system name keyword or file system status, and view their basic information.In the upper right corner of the page, click Search by", "product_code":"sfs", "title":"Viewing a File System", - "uri":"en-us_topic_0000001567076569.html", + "uri":"en-us_topic_0000001476461694.html", "doc_type":"usermanual", "p_code":"26", "code":"27" @@ -246,7 +246,7 @@ "desc":"Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.The file sys", "product_code":"sfs", "title":"Deleting a File System", - "uri":"en-us_topic_0000001515917216.html", + "uri":"en-us_topic_0000001527141597.html", "doc_type":"usermanual", "p_code":"26", "code":"28" @@ -417,7 +417,7 @@ "desc":"When a file system is mounted to servers using the mount command, message timed out is displayed.Cause 1: The network status is not stable.Cause 2: The network connection", "product_code":"sfs", "title":"Mounting a File System Times Out", - "uri":"en-us_topic_0000001515917172.html", + "uri":"en-us_topic_0037934210.html", "doc_type":"usermanual", "p_code":"46", "code":"47" @@ -567,7 +567,7 @@ "code":"63" }, { - "desc":"SFS Capacity-Oriented supports standard NFSv3. SFS Turbo supports the standard NFSv3 protocol.SFS Capacity-Oriented and SFS Turbo all support the standard NFSv3 protocol.", + "desc":"SFS Capacity-Oriented and SFS Turbo all support the standard NFSv3 protocol.", "product_code":"sfs", "title":"What Access Protocols Are Supported by SFS?", "uri":"sfs_01_0072.html", diff --git a/docs/sfs/umn/en-us_topic_0000001476461694.html b/docs/sfs/umn/en-us_topic_0000001476461694.html new file mode 100644 index 000000000..8f1cdaead --- /dev/null +++ b/docs/sfs/umn/en-us_topic_0000001476461694.html @@ -0,0 +1,76 @@ + + +

Viewing a File System

+

You can search for file systems by file system name keyword or file system status, and view their basic information.

+

Procedure

  1. Log in to the SFS console.
  2. In the file system list, view the file systems you have created. Table 1 describes the file system parameters.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Name

    +

    Name of the file system, for example, sfs-name-001

    +

    AZ

    +

    Availability zone where the file system is located

    +

    Status

    +

    Possible values are Available, Unavailable, Frozen, Creating, Deleting, Deletion error, Creation failed, Expanding, Expansion error, Capacity reducing, Capacity reduction error, and Capacity reduction failed.

    +

    Protocol Type

    +

    File system protocol, which is NFS

    +

    Available Capacity (GB)

    +

    Remaining file system space available to data storage

    +
    NOTE:

    This information is refreshed every 15 minutes.

    +
    +

    Maximum Capacity (GB)

    +

    Maximum capacity of the file system

    +

    Encrypted

    +

    Encryption status of the file system. The value can be Yes or No.

    +

    Mount Point

    +

    File system mount point, which is in the format of File system domain name:/Path or File system IP address:/

    +
    NOTE:

    If the mount point is too long to display completely, adjust the column width.

    +
    +

    Operation

    +

    For an SFS Capacity-Oriented file system, operations include resizing, deletion, and monitoring metric viewing.

    +

    For an SFS Turbo file system, operations include capacity expansion, deletion, and monitoring metric viewing.

    +
    +
    +

  3. Click the name of a file system to view detailed information about the file system. See Figure 1.

    Figure 1 File system information
    +

  4. (Optional) Search for file systems by file system name keyword, key ID, or file system status.

    In the upper right corner of the page, click Search by Tag to query file systems by tag.
    • On the displayed Search by Tag tab page, enter a tag key and a tag value (must be among existing keys and values) and click Search.
    • You can use more than one tag for a combination search. Each time after a key and a value are entered, click . The added search criteria are displayed under the text boxes. When more than one tag is added, they will be applied together for a combination search. A maximum of 10 tags can be added at a time.
    • You can click Reset under the search criteria to reset.
    +
    +

+
+
+
+
+
Parent topic: File System Management
+
+
+ diff --git a/docs/sfs/umn/en-us_topic_0000001515917172.html b/docs/sfs/umn/en-us_topic_0000001515917172.html deleted file mode 100644 index bd0e1fe2d..000000000 --- a/docs/sfs/umn/en-us_topic_0000001515917172.html +++ /dev/null @@ -1,37 +0,0 @@ - - -

Mounting a File System Times Out

-

Symptom

When a file system is mounted to servers using the mount command, message timed out is displayed.

-
-

Possible Causes

  • Cause 1: The network status is not stable.
  • Cause 2: The network connection is abnormal.
  • Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.
  • Cause 4: The server where the file system is to be mounted runs Ubuntu18 or later.
-
-

Fault Diagnosis

After the network fault is excluded, run the mount command again.

-
-

Solution

  • Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.

    Re-mount the file system after the network issue is addressed.

    -
    • If the patch is uninstalled successfully, no further action is required.
    • If the problem persists, see the solution for cause 3.
    -
  • Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.
    1. Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
      • If the DNS has not been configured, configure it. For details about how to configure the DNS, see Configuring DNS.
      • If the DNS has been configured, run the following command to check whether the DNS is correct:

        nslookup File system domain name

        -

        If the resolved IP address is in network segment 100, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to 2.

        -
      -
    2. Modify the /etc/resolv.conf configuration file, configure the correct tenant DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.
      Figure 1 Configuring DNS
      -
      The format is as follows:
      nameserver 100.125.4.25
      -
      -
      • If the configuration succeeds, go to 3.
      • If the configuration fails, run the lsattr /etc/resolv.conf command. If the information shown in Figure 2 is displayed, the file is locked.
        Figure 2 A locked file
        -

        Run the chattr -i/etc/resolv.conf command to unlock the file. Then, re-configure the DNS and go to 3.

        -
      -
    3. Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
    4. The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See Figure 3 and Figure 4.
      Figure 3 VPC details
      -

      -
      Figure 4 Modifying the DNS
      -
    5. (Optional) Restart the server.
    6. Run the mount command again.
      • If the problem is solved, no further action is required.
      • If the problem persists, see the solution for cause 4.
      -
    -
  • Cause 4: The server where the file system is to be mounted runs Ubuntu18 or later.
    1. Reconfigure DNS by referring to Configuring DNS.
    2. Check whether the target server running Ubuntu18 or later uses a private image.
      • If yes, go to 4.
      • If no, go to 3.
      -
    3. Convert the public image server to a private image server.
      1. To create a private image based on an existing ECS, see section "Creating an Image" in the Elastic Cloud Server User Guide.
      2. Use the private image created in 3.a to create an ECS or change the ECS OS using the private image created in 3.a. For details, see section "Changing the OS" in the Elastic Cloud Server User Guide.
      -
    4. Log in to the server and mount the file system again.
    -
-
-
-
-
-
Parent topic: Troubleshooting
-
-
- diff --git a/docs/sfs/umn/en-us_topic_0000001515917216.html b/docs/sfs/umn/en-us_topic_0000001515917216.html deleted file mode 100644 index 6db0fc17c..000000000 --- a/docs/sfs/umn/en-us_topic_0000001515917216.html +++ /dev/null @@ -1,19 +0,0 @@ - - -

Deleting a File System

-

Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.

-

Prerequisites

The file system to be deleted has been unmounted. For details about how to unmount the file system, see Unmount a File System.

-
-

Procedure

  1. Log in to SFS Console.
  2. In the file system list, locate the file system you want to delete and click Delete in the Operation column.

    If you want to delete more than one file system at a time, select the file systems, and then click Delete in the upper left part of the file system list. In the displayed dialog box, confirm the information, enter Delete in the text box, and then click Yes. Batch deletion is only supported for SFS Capacity-Oriented file systems.

    -

  3. In the displayed dialog box, as shown in Figure 1, confirm the information and then click Yes.

    Only Available and Unavailable file systems can be deleted.

    -
    -
    Figure 1 Deleting a file system
    -

  4. Check that the file system disappears from the file system list.
-
-
-
-
-
Parent topic: File System Management
-
-
- diff --git a/docs/sfs/umn/en-us_topic_0000001527141597.html b/docs/sfs/umn/en-us_topic_0000001527141597.html new file mode 100644 index 000000000..f5ff914a0 --- /dev/null +++ b/docs/sfs/umn/en-us_topic_0000001527141597.html @@ -0,0 +1,19 @@ + + +

Deleting a File System

+

Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.

+

Prerequisites

The file system to be deleted has been unmounted. For details about how to unmount the file system, see Unmount a File System.

+
+

Procedure

  1. Log in to SFS Console.
  2. In the file system list, locate the file system you want to delete and click Delete in the Operation column.

    If you want to delete more than one file system at a time, select the file systems, and then click Delete in the upper left part of the file system list. In the displayed dialog box, confirm the information, enter Delete in the text box, and then click Yes. Batch deletion is only supported for SFS Capacity-Oriented file systems.

    +

  3. In the displayed dialog box, as shown in Figure 1, confirm the information and then click Yes.

    Only Available and Unavailable file systems can be deleted.

    +
    +
    Figure 1 Deleting a file system
    +

  4. Check that the file system disappears from the file system list.
+
+
+
+
+
Parent topic: File System Management
+
+
+ diff --git a/docs/sfs/umn/en-us_topic_0000001567076569.html b/docs/sfs/umn/en-us_topic_0000001567076569.html deleted file mode 100644 index e2475f8ce..000000000 --- a/docs/sfs/umn/en-us_topic_0000001567076569.html +++ /dev/null @@ -1,76 +0,0 @@ - - -

Viewing a File System

-

You can search for file systems by file system name keyword or file system status, and view their basic information.

-

Procedure

  1. Log in to the SFS console.
  2. In the file system list, view the file systems you have created. Table 1 describes the file system parameters.

    -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 Parameter description

    Parameter

    -

    Description

    -

    Name

    -

    Name of the file system, for example, sfs-name-001

    -

    AZ

    -

    Availability zone where the file system is located

    -

    Status

    -

    Possible values are Available, Unavailable, Frozen, Creating, Deleting, Deletion error, Creation failed, Expanding, Expansion error, Capacity reducing, Capacity reduction error, and Capacity reduction failed.

    -

    Protocol Type

    -

    File system protocol, which is NFS

    -

    Available Capacity (GB)

    -

    Remaining file system space available to data storage

    -
    NOTE:

    This information is refreshed every 15 minutes.

    -
    -

    Maximum Capacity (GB)

    -

    Maximum capacity of the file system

    -

    Encrypted

    -

    Encryption status of the file system. The value can be Yes or No.

    -

    Mount Point

    -

    File system mount point, which is in the format of File system domain name:/Path or File system IP address:/

    -
    NOTE:

    If the mount point is too long to display completely, adjust the column width.

    -
    -

    Operation

    -

    For an SFS Capacity-Oriented file system, operations include resizing, deletion, and monitoring metric viewing.

    -

    For an SFS Turbo file system, operations include capacity expansion, deletion, and monitoring metric viewing.

    -
    -
    -

  3. Click the name of a file system to view detailed information about the file system. See Figure 1.

    Figure 1 File system information
    -

  4. (Optional) Search for file systems by file system name keyword, key ID, or file system status.

    In the upper right corner of the page, click Search by Tag to query file systems by tag.
    • On the displayed Search by Tag tab page, enter a tag key and a tag value (must be among existing keys and values) and click Search.
    • You can use more than one tag for a combination search. Each time after a key and a value are entered, click . The added search criteria are displayed under the text boxes. When more than one tag is added, they will be applied together for a combination search. A maximum of 10 tags can be added at a time.
    • You can click Reset under the search criteria to reset.
    -
    -

-
-
-
-
-
Parent topic: File System Management
-
-
- diff --git a/docs/sfs/umn/en-us_topic_0000001567076661.html b/docs/sfs/umn/en-us_topic_0000001567076661.html deleted file mode 100644 index 95011de53..000000000 --- a/docs/sfs/umn/en-us_topic_0000001567076661.html +++ /dev/null @@ -1,167 +0,0 @@ - - -

Mounting an NFS File System to ECSs (Linux)

-

After creating a file system, you need to mount the file system to servers so that they can share the file system.

-

In this section, ECSs are used as example servers. Operations on BMSs and containers (CCE) are the same as those on ECSs.

-

Prerequisites

  • You have checked the type of the operating system on each ECS. Different operating systems use different commands to install the NFS client.
  • 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. SFS Turbo file systems do not require domain name resolution.
-
-

Procedure

  1. Log in to the management console using a cloud account.

    1. Log in to the management console and select a region and a project.
    2. Under Computing, click Elastic Cloud Server to go to the ECS console.
    -

  2. Log in to the ECS as user root.

    If you log in to the ECS as a non-root user, see Mounting a File System to a Linux ECS as a Non-root User.

    -
    -

  3. Install the NFS client.

    1. Run the following command to check whether the NFS software package is installed.
      • On CentOS, Red Hat, Oracle Enterprise Linux, SUSE, EulerOS, Fedora, or OpenSUSE:

        rpm -qa|grep nfs

        -
      • On Debian or Ubuntu:

        dpkg -l nfs-common

        -
      -
      If a command output similar to the following is displayed, the NFS software package has been installed and you can go to 4. If nothing is displayed, go to 3.b.
      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
        libnfsidmap
-nfs-utils
        -
      • On SUSE or OpenSUSE:
        nfsidmap
-nfs-client
        -
      • On Debian or Ubuntu:
        nfs-common
        -
      -
      -
    2. Run the following command to install the NFS software package.

      The following commands require that ECSs be connected to the Internet. Or, the installation will fail. Installing NFS clients requires enabling effective software repositories. Installing NFS clients will fail if no software repository is enabled or the ECS does not have any software repository. If installing NFS clients fails, refer to Enabling or Adding a Software Repository.

      -
      -
      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:

        sudo yum -y install nfs-utils

        -
      • On Debian or Ubuntu:

        sudo apt-get install nfs-common

        -
      • On SUSE or OpenSUSE:

        zypper install nfs-client

        -
      -
    -

  4. Run the following command to check whether the domain name in the file system mount point can be resolved. SFS Turbo file systems do not require domain name resolution. Skip this step and directly mount the file system.

    nslookup File system domain name

    -
    • A file system domain name is just a part of the mount point, for example, sfs-nas1.xxxx.com. You can obtain a file system domain name from the mount point of a file system. In this step, you are not supposed to enter the entire mount point but only the domain name.
    • If the nslookup command cannot be used, install the bind-utils software package by running the yum install bind-utils command.
    -
    -
    • If the domain name can be resolved, go to 5.
    • If the domain name cannot be resolved, configure the DNS server IP address and then mount the file system. For details, see Configuring DNS.
    -

  5. Run the following command to create a local path for mounting the file system:

    mkdir Local path

    -

    If there is any resource, such as a disk, already mounted on the local path, create a new path. (NFS clients do not refuse repeated mounts. If there are repeated mounts, information of the last successful mount is displayed.)

    -
    -

  6. Run the following command to mount the file system to the ECS that belongs to the same VPC as the file system. Currently, the file system can be mounted to Linux ECSs using NFSv3 only.

    Table 1 describes the variables.

    -

    To mount an SFS Capacity-Oriented file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path

    -

    To mount an SFS Turbo file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path

    -

    After an ECS where file systems have been mounted restarts, it loses the file system mount information. You can configure automatic mount in the fstab file to ensure that an ECS automatically mounts file systems when it restarts. For details, see Mounting a File System Automatically.

    -
    -
    -
    - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 Parameter description

    Parameter

    -

    Description

    -

    vers

    -

    File system version. Only NFSv3 is supported currently, so the value is fixed to 3.

    -

    timeo

    -

    Waiting time before the NFS client retransmits a request. The unit is 0.1 second. The recommended value is 600.

    -

    resvport/noresvport

    -

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    -

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    -

    lock/nolock

    -

    Whether to lock files on the server using the NLM protocol. If nolock is selected, the lock is valid for applications on one host. For applications on another host, the lock is invalid. The recommended value is nolock. If this parameter is not specified, lock is selected by default. In this case, other servers cannot write data to the file system.

    -

    Mount point

    -

    The format for an SFS Capacity-Oriented file system is File system domain name:/Path, for example, example.com:/share-xxx. The format for an SFS Turbo file system is File system IP address:/, for example, 192.168.0.0:/.

    -

    See Figure 1.

    -
    NOTE:
    • x is a digit or letter.
    • If the mount point is too long to display completely, you can adjust the column width.
    • Hover the mouse over the mount point to display the complete mount command.
    -
    -

    Local path

    -

    Local path on the ECS, used to mount the file system, for example, /local_path.

    -
    -
    -
    -
    Figure 1 Mount point
    -

    For more mounting parameters for performance optimization during file system mounting, see Table 2. Use commas (,) to separate parameters. The following command is an example:

    -

    mount -t nfs -o vers=3,timeo=600,nolock,rsize=1048576,wsize=1048576,hard,retrans=3,noresvport,ro,async,noatime,nodiratime Mount point Local path

    - -
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 2 Parameters for file system mounting

    Parameter

    -

    Description

    -

    rsize

    -

    Maximum number of bytes that can be read from the server each time. The actual data is less than or equal to the value of this parameter. The value of rsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    -

    You are advised to set this parameter to the maximum value 1048576.

    -

    wsize

    -

    Maximum number of bytes that can be written to the server each time. The actual data is less than or equal to the value of this parameter. The value of wsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    -

    You are advised to set this parameter to the maximum value 1048576.

    -

    soft/hard

    -

    soft indicates that a file system is mounted in soft mount mode. In this mode, if an NFS request times out, the client returns an error to the invoking program. hard indicates that a file system is mounted in hard mount mode. In this mode, if the NFS request times out, the client continues to request until the request is successful.

    -

    The default value is hard.

    -

    retrans

    -

    Number of retransmission times before the client returns an error.

    -

    ro/rw

    -
    • ro: indicates that the file system is mounted as read-only.
    • rw: indicates that the file system is mounted as read/write.
    -

    The default value is rw. If this parameter is not specified, the file system will be mounted as read/write.

    -

    resvport/noresvport

    -

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    -

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    -

    sync/async

    -

    sync indicates that data is written to the server immediately. async indicates that data is first written to the cache before being written to the server.

    -

    Synchronous write requires that an NFS server returns a success message only after all data is written to the server, which brings long latency. The recommended value is async.

    -

    noatime

    -

    If you do not need to record the file access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    -

    nodiratime

    -

    If you do not need to record the directory access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    -
    -
    -

    You are advised to use the default values for the parameters without usage recommendations.

    -
    -

  7. Run the following command to view the mounted file system:

    mount -l

    -
    If the command output contains the following information, the file system has been mounted.
    Mount point on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
    -
    -

  8. After the file system is mounted successfully, access the file system on the ECSs to read or write data.

    If the mounting fails or times out, rectify the fault by referring to Troubleshooting.

    -

    The maximum size of a file that can be written to an SFS Capacity-Oriented file system is 240 TB.

    -

    The maximum size of a file that can be written to an SFS Turbo file system is 32 TB, and that for an SFS Turbo Enhanced file system is 320 TB.

    -
    -
    -

-
-
-
-
-
Parent topic: Mount a File System
-
-
- diff --git a/docs/sfs/umn/en-us_topic_0034428728.html b/docs/sfs/umn/en-us_topic_0034428728.html new file mode 100644 index 000000000..bfcb78c4d --- /dev/null +++ b/docs/sfs/umn/en-us_topic_0034428728.html @@ -0,0 +1,167 @@ + + +

Mounting an NFS File System to ECSs (Linux)

+

After creating a file system, you need to mount the file system to servers so that they can share the file system.

+

In this section, ECSs are used as example servers. Operations on BMSs and containers (CCE) are the same as those on ECSs.

+

Prerequisites

  • You have checked the type of the operating system on each ECS. Different operating systems use different commands to install the NFS client.
  • 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. SFS Turbo file systems do not require domain name resolution.
+
+

Procedure

  1. Log in to the management console using a cloud account.

    1. Log in to the management console and select a region and a project.
    2. Under Computing, click Elastic Cloud Server to go to the ECS console.
    +

  2. Log in to the ECS as user root.

    If you log in to the ECS as a non-root user, see Mounting a File System to a Linux ECS as a Non-root User.

    +
    +

  3. Install the NFS client.

    1. Run the following command to check whether the NFS software package is installed.
      • On CentOS, Red Hat, Oracle Enterprise Linux, SUSE, EulerOS, Fedora, or OpenSUSE:

        rpm -qa|grep nfs

        +
      • On Debian or Ubuntu:

        dpkg -l nfs-common

        +
      +
      If a command output similar to the following is displayed, the NFS software package has been installed and you can go to 4. If nothing is displayed, go to 3.b.
      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
        libnfsidmap
+nfs-utils
        +
      • On SUSE or OpenSUSE:
        nfsidmap
+nfs-client
        +
      • On Debian or Ubuntu:
        nfs-common
        +
      +
      +
    2. Run the following command to install the NFS software package.

      The following commands require that ECSs be connected to the Internet. Or, the installation will fail. Installing NFS clients requires enabling effective software repositories. Installing NFS clients will fail if no software repository is enabled or the ECS does not have any software repository. If installing NFS clients fails, refer to Enabling or Adding a Software Repository.

      +
      +
      • On CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:

        sudo yum -y install nfs-utils

        +
      • On Debian or Ubuntu:

        sudo apt-get install nfs-common

        +
      • On SUSE or OpenSUSE:

        zypper install nfs-client

        +
      +
    +

  4. Run the following command to check whether the domain name in the file system mount point can be resolved. SFS Turbo file systems do not require domain name resolution. Skip this step and directly mount the file system.

    nslookup File system domain name

    +
    • A file system domain name is just a part of the mount point, for example, sfs-nas1.xxxx.com. You can obtain a file system domain name from the mount point of a file system. In this step, you are not supposed to enter the entire mount point but only the domain name.
    • If the nslookup command cannot be used, install the bind-utils software package by running the yum install bind-utils command.
    +
    +
    • If the domain name can be resolved, go to 5.
    • If the domain name cannot be resolved, configure the DNS server IP address and then mount the file system. For details, see Configuring DNS.
    +

  5. Run the following command to create a local path for mounting the file system:

    mkdir Local path

    +

    If there is any resource, such as a disk, already mounted on the local path, create a new path. (NFS clients do not refuse repeated mounts. If there are repeated mounts, information of the last successful mount is displayed.)

    +
    +

  6. Run the following command to mount the file system to the ECS that belongs to the same VPC as the file system. Currently, the file system can be mounted to Linux ECSs using NFSv3 only.

    Table 1 describes the variables.

    +

    To mount an SFS Capacity-Oriented file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path

    +

    To mount an SFS Turbo file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path

    +

    After an ECS where file systems have been mounted restarts, it loses the file system mount information. You can configure automatic mount in the fstab file to ensure that an ECS automatically mounts file systems when it restarts. For details, see Mounting a File System Automatically.

    +
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    vers

    +

    File system version. Only NFSv3 is supported currently, so the value is fixed to 3.

    +

    timeo

    +

    Waiting time before the NFS client retransmits a request. The unit is 0.1 second. The recommended value is 600.

    +

    resvport/noresvport

    +

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    +

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    +

    lock/nolock

    +

    Whether to lock files on the server using the NLM protocol. If nolock is selected, the lock is valid for applications on one host. For applications on another host, the lock is invalid. The recommended value is nolock. If this parameter is not specified, lock is selected by default. In this case, other servers cannot write data to the file system.

    +

    Mount point

    +

    The format for an SFS Capacity-Oriented file system is File system domain name:/Path, for example, example.com:/share-xxx. The format for an SFS Turbo file system is File system IP address:/, for example, 192.168.0.0:/.

    +

    See Figure 1.

    +
    NOTE:
    • x is a digit or letter.
    • If the mount point is too long to display completely, you can adjust the column width.
    • Hover the mouse over the mount point to display the complete mount command.
    +
    +

    Local path

    +

    Local path on the ECS, used to mount the file system, for example, /local_path.

    +
    +
    +
    +
    Figure 1 Mount point
    +

    For more mounting parameters for performance optimization during file system mounting, see Table 2. Use commas (,) to separate parameters. The following command is an example:

    +

    mount -t nfs -o vers=3,timeo=600,nolock,rsize=1048576,wsize=1048576,hard,retrans=3,noresvport,ro,async,noatime,nodiratime Mount point Local path

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Parameters for file system mounting

    Parameter

    +

    Description

    +

    rsize

    +

    Maximum number of bytes that can be read from the server each time. The actual data is less than or equal to the value of this parameter. The value of rsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    +

    You are advised to set this parameter to the maximum value 1048576.

    +

    wsize

    +

    Maximum number of bytes that can be written to the server each time. The actual data is less than or equal to the value of this parameter. The value of wsize must be a positive integer that is a multiple of 1024. If the entered value is smaller than 1024, the value is automatically set to 4096. If the entered value is greater than 1048576, the value is automatically set to 1048576. By default, the setting is performed after the negotiation between the server and the client.

    +

    You are advised to set this parameter to the maximum value 1048576.

    +

    soft/hard

    +

    soft indicates that a file system is mounted in soft mount mode. In this mode, if an NFS request times out, the client returns an error to the invoking program. hard indicates that a file system is mounted in hard mount mode. In this mode, if the NFS request times out, the client continues to request until the request is successful.

    +

    The default value is hard.

    +

    retrans

    +

    Number of retransmission times before the client returns an error.

    +

    ro/rw

    +
    • ro: indicates that the file system is mounted as read-only.
    • rw: indicates that the file system is mounted as read/write.
    +

    The default value is rw. If this parameter is not specified, the file system will be mounted as read/write.

    +

    resvport/noresvport

    +

    Whether the confidential source port is used for server connection. By default, resvport indicates that the confidential port is used, and noresvport indicates that the confidential port is not used. The kernel version is 2.6.28 or later.

    +

    You are advised to set this parameter to noresvport so that a new TCP port can be used when the network is reconnected. This ensures that the connection is not interrupted when the network recovers from a fault.

    +

    sync/async

    +

    sync indicates that data is written to the server immediately. async indicates that data is first written to the cache before being written to the server.

    +

    Synchronous write requires that an NFS server returns a success message only after all data is written to the server, which brings long latency. The recommended value is async.

    +

    noatime

    +

    If you do not need to record the file access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    +

    nodiratime

    +

    If you do not need to record the directory access time, set this parameter. This prevents overheads caused by access time modification during frequent access.

    +
    +
    +

    You are advised to use the default values for the parameters without usage recommendations.

    +
    +

  7. Run the following command to view the mounted file system:

    mount -l

    +
    If the command output contains the following information, the file system has been mounted.
    Mount point on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
    +
    +

  8. After the file system is mounted successfully, access the file system on the ECSs to read or write data.

    If the mounting fails or times out, rectify the fault by referring to Troubleshooting.

    +

    The maximum size of a file that can be written to an SFS Capacity-Oriented file system is 240 TB.

    +

    The maximum size of a file that can be written to an SFS Turbo file system is 32 TB, and that for an SFS Turbo Enhanced file system is 320 TB.

    +
    +
    +

+
+
+
+
+
Parent topic: Mount a File System
+
+
+ diff --git a/docs/sfs/umn/en-us_topic_0037934210.html b/docs/sfs/umn/en-us_topic_0037934210.html new file mode 100644 index 000000000..6e7463646 --- /dev/null +++ b/docs/sfs/umn/en-us_topic_0037934210.html @@ -0,0 +1,37 @@ + + +

Mounting a File System Times Out

+

Symptom

When a file system is mounted to servers using the mount command, message timed out is displayed.

+
+

Possible Causes

  • Cause 1: The network status is not stable.
  • Cause 2: The network connection is abnormal.
  • Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.
  • Cause 4: The server where the file system is to be mounted runs Ubuntu18 or later.
+
+

Fault Diagnosis

After the network fault is excluded, run the mount command again.

+
+

Solution

  • Cause 1 and Cause 2: The network status is not stable or the network connection is abnormal.

    Re-mount the file system after the network issue is addressed.

    +
    • If the patch is uninstalled successfully, no further action is required.
    • If the problem persists, see the solution for cause 3.
    +
  • Cause 3: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.
    1. Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
      • If the DNS has not been configured, configure it. For details about how to configure the DNS, see Configuring DNS.
      • If the DNS has been configured, run the following command to check whether the DNS is correct:

        nslookup File system domain name

        +

        If the resolved IP address is in network segment 100, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to 2.

        +
      +
    2. Modify the /etc/resolv.conf configuration file, configure the correct tenant DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 100.125.4.25.
      Figure 1 Configuring DNS
      +
      The format is as follows:
      nameserver 100.125.4.25
      +
      +
      • If the configuration succeeds, go to 3.
      • If the configuration fails, run the lsattr /etc/resolv.conf command. If the information shown in Figure 2 is displayed, the file is locked.
        Figure 2 A locked file
        +

        Run the chattr -i/etc/resolv.conf command to unlock the file. Then, re-configure the DNS and go to 3.

        +
      +
    3. Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
    4. The default DNS of the ECS applied by the user is inherited from the VPC to which the ECS belongs. Therefore, when the ECS restarts, the ECS changes synchronously. For this reason, changing configurations of the ECS does not settle the issue completely. You need to modify configurations in the VPC. Set a correct tenant DNS for the subnet of the VPC to which the ECS belongs. See Figure 3 and Figure 4.
      Figure 3 VPC details
      +

      +
      Figure 4 Modifying the DNS
      +
    5. (Optional) Restart the server.
    6. Run the mount command again.
      • If the problem is solved, no further action is required.
      • If the problem persists, see the solution for cause 4.
      +
    +
  • Cause 4: The server where the file system is to be mounted runs Ubuntu18 or later.
    1. Reconfigure DNS by referring to Configuring DNS.
    2. Check whether the target server running Ubuntu18 or later uses a private image.
      • If yes, go to 4.
      • If no, go to 3.
      +
    3. Convert the public image server to a private image server.
      1. To create a private image based on an existing ECS, see section "Creating an Image" in the Elastic Cloud Server User Guide.
      2. Use the private image created in 3.a to create an ECS or change the ECS OS using the private image created in 3.a. For details, see section "Changing the OS" in the Elastic Cloud Server User Guide.
      +
    4. Log in to the server and mount the file system again.
    +
+
+
+
+
+
Parent topic: Troubleshooting
+
+
+ diff --git a/docs/sfs/umn/sfs_01_0007.html b/docs/sfs/umn/sfs_01_0007.html index 8eb242094..8d5184c79 100644 --- a/docs/sfs/umn/sfs_01_0007.html +++ b/docs/sfs/umn/sfs_01_0007.html @@ -14,7 +14,7 @@

Elastic Cloud Server (ECS)

-

Mounting an NFS File System to ECSs (Linux)

+

Mounting an NFS File System to ECSs (Linux)

Mounting an NFS File System to ECSs (Windows)

diff --git a/docs/sfs/umn/sfs_01_0024.html b/docs/sfs/umn/sfs_01_0024.html index 24d80cd1f..7d9e62b42 100644 --- a/docs/sfs/umn/sfs_01_0024.html +++ b/docs/sfs/umn/sfs_01_0024.html @@ -8,7 +8,7 @@
    -
  • Mounting an NFS File System to ECSs (Linux)
    +
  • Mounting an NFS File System to ECSs (Linux)
  • Mounting an NFS File System to ECSs (Windows)
    • diff --git a/docs/sfs/umn/sfs_01_0025.html b/docs/sfs/umn/sfs_01_0025.html index 198978b00..281bf148c 100644 --- a/docs/sfs/umn/sfs_01_0025.html +++ b/docs/sfs/umn/sfs_01_0025.html @@ -27,12 +27,12 @@

    Mount point

    -

    Mount object, that is, the mount point of the file system to be mounted. Set this parameter to the mount point in the mount command that is used in Mounting an NFS File System to ECSs (Linux).

    +

    Mount object, that is, the mount point of the file system to be mounted. Set this parameter to the mount point in the mount command that is used in Mounting an NFS File System to ECSs (Linux).

    /local_path

    -

    Mount point, that is, the directory created on the ECS for mounting the file system. Set this parameter to the local path in the mount command that is used in Mounting an NFS File System to ECSs (Linux).

    +

    Mount point, that is, the directory created on the ECS for mounting the file system. Set this parameter to the local path in the mount command that is used in Mounting an NFS File System to ECSs (Linux).

    nfs

    diff --git a/docs/sfs/umn/sfs_01_0034.html b/docs/sfs/umn/sfs_01_0034.html index 2e31efb35..2304936f2 100644 --- a/docs/sfs/umn/sfs_01_0034.html +++ b/docs/sfs/umn/sfs_01_0034.html @@ -4,9 +4,9 @@
    diff --git a/docs/sfs/umn/sfs_01_0043.html b/docs/sfs/umn/sfs_01_0043.html index 45ab9a3b8..9a9c23485 100644 --- a/docs/sfs/umn/sfs_01_0043.html +++ b/docs/sfs/umn/sfs_01_0043.html @@ -4,8 +4,8 @@

    This section describes how to add tags to existing file systems. You can also add tags when creating file systems. For details, see section 4.2 Creating a File System.

    Tags are used to identify and classify file systems.

    • Tags are composed of key-value pairs.
      • A tag key can contain a maximum of 36 characters and cannot be left blank. It can only contain letters, digits, hyphens (-), and underscores (_).
      • A tag value can contain a maximum of 43 characters and can be an empty string. It can only contain letters, digits, hyphens (-), and underscores (_).
      -
    • You can add a maximum of 10 tags to one file system.
    • The tag keys of the same file system must be unique.
    • Once created, the tag keys of the file system cannot be edited. You can only edit the tag values. You can delete tags.
    -

    Procedure

    1. Log in to SFS Console.
    2. In the file system list, find the file system to which you want to add tags and click the name of it. The file system details page is displayed, as shown in Figure 1.

      Figure 1 Managing file system tags
      +
    3. You can add a maximum of 20 tags to one file system.
    4. The tag keys of the same file system must be unique.
    5. Once created, the tag keys of the file system cannot be edited. You can only edit the tag values. You can delete tags.
+

Procedure

  1. Log in to the SFS console.
  2. In the file system list, find the file system to which you want to add tags and click the name of it. The file system details page is displayed, as shown in Figure 1.

    Figure 1 Managing file system tags

  3. Click the Tags tab.
  4. On the Tags tab page, click Add Tag. The Add Tag dialog box is displayed.
  5. Add the key and value of the tag and click OK.

    • Key: This parameter is mandatory.
    • Value: This parameter is optional.

    Return to the tag list, and you can see the tags you have just added. You can edit and delete the added tags.

diff --git a/docs/sfs/umn/sfs_01_0052.html b/docs/sfs/umn/sfs_01_0052.html index e8ebe421c..08a45385a 100644 --- a/docs/sfs/umn/sfs_01_0052.html +++ b/docs/sfs/umn/sfs_01_0052.html @@ -11,7 +11,7 @@

Prerequisites

  • A VPC has been created.
  • ECSs that function as head nodes and compute nodes have been created, and have been assigned to the VPC.
  • SFS has been enabled.
-

Example Configuration

  1. Log in to SFS Console.
  2. In the upper right corner of the page, click Create File System.
  3. On the Create File System page, set parameters as instructed.
  4. After the configuration is complete, click Create Now.

    To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    +

    Example Configuration

    1. Log in to SFS Console.
    2. In the upper right corner of the page, click Create File System.
    3. On the Create File System page, set parameters as instructed.
    4. After the configuration is complete, click Create Now.

      To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    5. Log in to the head node, and upload the files to the file system.
    6. Start gene sequencing, and the compute node obtains the gene sequencing file from the mounted file system for calculation.
diff --git a/docs/sfs/umn/sfs_01_0053.html b/docs/sfs/umn/sfs_01_0053.html index ae44eb6e4..7143ed83d 100644 --- a/docs/sfs/umn/sfs_01_0053.html +++ b/docs/sfs/umn/sfs_01_0053.html @@ -10,7 +10,7 @@

Prerequisites

  • A VPC has been created.
  • ECSs that function as upload workstations and editing workstations have been created, and have been assigned to the VPC.
  • SFS has been enabled.
-

Example Configuration

  1. Log in to SFS Console.
  2. In the upper right corner of the page, click Create File System.
  3. On the Create File System page, set parameters as instructed.
  4. After the configuration is complete, click Create Now.

    To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    +

    Example Configuration

    1. Log in to SFS Console.
    2. In the upper right corner of the page, click Create File System.
    3. On the Create File System page, set parameters as instructed.
    4. After the configuration is complete, click Create Now.

      To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    5. Log in to the upload workstations, and upload the material files to the file system.
    6. Log in to the editing workstations, and edit the material files.
diff --git a/docs/sfs/umn/sfs_01_0054.html b/docs/sfs/umn/sfs_01_0054.html index cf375188f..5557bb331 100644 --- a/docs/sfs/umn/sfs_01_0054.html +++ b/docs/sfs/umn/sfs_01_0054.html @@ -8,7 +8,7 @@

Prerequisites

  • A VPC has been created.
  • Servers that function as head nodes and compute nodes have been created, and have been assigned to the VPC.
  • SFS has been enabled.
-

Example Configuration

  1. Log in to SFS Console.
  2. In the upper right corner of the page, click Create File System.
  3. On the Create File System page, set parameters as instructed.
  4. After the configuration is complete, click Create Now.

    To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    +

    Example Configuration

    1. Log in to SFS Console.
    2. In the upper right corner of the page, click Create File System.
    3. On the Create File System page, set parameters as instructed.
    4. After the configuration is complete, click Create Now.

      To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    5. Log in to the head node and upload the files to the file system.
    6. Start the web server.
diff --git a/docs/sfs/umn/sfs_01_0055.html b/docs/sfs/umn/sfs_01_0055.html index de506cbfa..265a281da 100644 --- a/docs/sfs/umn/sfs_01_0055.html +++ b/docs/sfs/umn/sfs_01_0055.html @@ -8,7 +8,7 @@

Prerequisites

  • A VPC has been created.
  • Servers that function as head nodes and compute nodes have been created, and have been assigned to the VPC.
  • SFS has been enabled.
-

Example Configuration

  1. Log in to SFS Console.
  2. In the upper right corner of the page, click Create File System.
  3. On the Create File System page, set parameters as instructed.
  4. After the configuration is complete, click Create Now.

    To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    +

    Example Configuration

    1. Log in to SFS Console.
    2. In the upper right corner of the page, click Create File System.
    3. On the Create File System page, set parameters as instructed.
    4. After the configuration is complete, click Create Now.

      To mount a file system to Linux ECSs, see Mounting an NFS File System to ECSs (Linux). To mount a file system to Windows ECSs, see Mounting an NFS File System to ECSs (Windows).

    5. Configure the log directory to the shared file system. It is recommended that each host use different log files.
    6. Start applications.
diff --git a/docs/sfs/umn/sfs_01_0056.html b/docs/sfs/umn/sfs_01_0056.html index 612024a76..6ea05a11a 100644 --- a/docs/sfs/umn/sfs_01_0056.html +++ b/docs/sfs/umn/sfs_01_0056.html @@ -4,7 +4,7 @@
    -
  • Mounting a File System Times Out
    +
  • Mounting a File System Times Out
  • Mounting a File System Fails
    • diff --git a/docs/sfs/umn/sfs_01_0104.html b/docs/sfs/umn/sfs_01_0104.html index b0aa98cd8..11ec2dd17 100644 --- a/docs/sfs/umn/sfs_01_0104.html +++ b/docs/sfs/umn/sfs_01_0104.html @@ -8,7 +8,13 @@ -

    2023-02-20

    +

    2023-07-03

    + +

    Updated the following content:

    +

    Added the description about the maximum number of tags that can be added to a file system.

    + + +

    2023-02-20

    Updated the following content:

    Added section "Permissions."