Overview
Scalable File Service (SFS) provides scalable, high-performance (NAS) file storage. With SFS, you can enjoy shared file access spanning multiple Elastic Cloud Servers (ECSs), Bare Metal Servers (BMSs), and containers created on Cloud Container Engine (CCE). See Figure 1.
- +
- File sharing
Servers in multiple availability zones (AZs) of a same region can access the same file system concurrently and share files.
- Elastic scaling
Storage can be scaled up or down on demand to dynamically adapt to service changes without interrupting applications. You can complete resizing with a few clicks.
- Superior performance
SFS enables file system performance to increase as capacity grows, and it delivers a high data durability to support rapid service growth.
-The backend storage system supports both HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, which eliminate single-node faults.
+The backend storage system supports HDD and SSD storage media. It adopts a distributed architecture and uses full redundant design for modules, eliminating single-node faults.
- Seamless integration
SFS supports Network File System (NFS). With this standard protocol, a broad range of mainstream applications can read and write data in the file system.
- Easy operation
In an intuitive graphical user interface (GUI), you can create and manage file systems with ease.
Accessing SFS
You can access SFS on the management console or via APIs by sending HTTPS requests.
+Accessing SFS
You can access SFS on the management console or through APIs by sending HTTPS requests.
- APIs
Use APIs if you need to integrate SFS into a third-party system for secondary development. For detailed operations, see Scalable File Service API Reference.
- Management console
Use the console if you prefer a web-based UI to perform operations.
Create a File System
You can create a file system and mount it to multiple servers. Then the servers can share this file system. You can create three types of file systems: SFS Capacity-Oriented, SFS Turbo, and General Purpose File System.
-Prerequisites
- Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
- - Before creating an SFS Turbo, SFS Capacity Oriented, or a general purpose file system, ensure that ECSs are available and are in the created VPC.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
+Prerequisites
- Before creating an SFS Turbo, SFS Capacity-Oriented, or a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
+ - Before creating an SFS Turbo SFS Capacity-Oriented or a general purpose file system, ensure that ECSs are available and are in the created VPC.
If no ECS is available, create an ECS by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
Creating an SFS Capacity-Oriented File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the upper right corner of the page, click Create File System.
- Set the parameters as described in Table 1 as shown in Figure 1. +
- In the upper right corner of the page, click Create File System.
- Set the parameters described in Table 1, as shown in Figure 1.
-
Table 1 File system parameters Parameter
A geographical area with an independent network and an independent power supply.
You are advised to select the AZ where the servers reside.
+You are advised to select the AZ where the ECSs reside.
Protocol Type
SFS supports NFS (only the NFSv3 protocol currently) for file system access.
+SFS supports NFS (NFSv3 only) for file system access.
-
-Creating a General Purpose File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane, choose General Purpose File System. In the upper right corner of the page, click Create File System.
- Set the file system parameters, as shown in Figure 2. Table 2 describes the parameters. +
- In the navigation pane, choose General Purpose File System. In the upper right corner of the page, click Create File System.
- Set the file system parameters, as shown in Figure 2. Table 2 describes the parameters.
- Click Create Now.
- Confirm the file system information and click Submit.
- Go back to the file system list.
If the file system is displayed in the list, it is successfully created. If it fails to be created, contact the website administrator.
Creating an SFS Turbo File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- Configure the parameters, as shown in Figure 3. Table 3 describes the parameters.
+
Creating an SFS Turbo File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- Configure the parameters, as shown in Figure 3. Table 3 describes the parameters.
@@ -208,7 +222,7 @@
File System 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.
+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.
@@ -251,12 +265,12 @@-
Cloud Backup and Recovery
+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 Not required is preselected:
+The following options are available, among which Not required is preselected:
- Not required: Backup is not configured. If you need backup protection after a file system has been created, log in to the CBR console, locate the desired vault, and associate the file system with the vault.
- Use existing vault
- Select an existing cloud backup vault from the drop-down list.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
- Auto assign
- Enter a vault name, which can contain a maximum of 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx.
- Enter a vault capacity, which is required for backing up SFS Turbo file systems. The vault capacity cannot be less than the size of file systems, so enter a value ranging from the total size of the associated file systems to 10,485,760, in the unit of GB.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
- Auto assign
- Enter a vault name, which can contain a maximum of 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx.
- Enter a vault capacity, which is required for backing up SFS Turbo file systems. The vault capacity cannot be less than the size of file systems, so enter a value ranging from the total size of the associated file systems to 10,485,760, in the unit of GB.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
-
@@ -265,8 +279,8 @@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 Encryption is selected, the following parameters will be displayed:
-- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see "Creating a CMK" in the Key Management Service User Guide.
+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 Encryption is selected, the following parameters will be displayed:
+- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see section "Creating a Custom Key" in the Key Management Service User Guide.
- KMS key ID
After you select a key name, the system automatically shows the key ID.
- Key Encryption Algorithm
After you select a key name, the system automatically shows the encryption algorithm of the key.
- KMS key name
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.- Key: Mandatory if the file system is going to be tagged
A tag key can contain a maximum of 36 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
- - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
A tag is composed of a key-value pair.- Key: Mandatory if the file system is going to be tagged
A tag key can contain a maximum of 128 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
+ - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 255 characters, including letters, digits, hyphens (-), and underscores (_).
- You can add a maximum of 20 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
- Log in to the management console using a cloud account.
- Log in to the management console using a cloud account.
- Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
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.
+ - Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
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.
- Before creating an SFS Turbo, SFS Capacity-Oriented, or a general purpose file system, ensure that a VPC is available.
Mounting an NFS File System to ECSs (Linux)
+After creating a file system, you need to mount the file system to cloud 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.
+General purpose file systems cannot be mounted to 32-bit Linux servers.
+Prerequisites
- You have checked the OS type of each ECS. Different OSs require 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 is in the same VPC as the file system is available.
- 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.
Constraints
This constraint only applies to local paths (mount points) and does not affect other files or directories.
+Metadata of the local paths (mount points) cannot be modified. Specifically, the following operations cannot be performed on the local paths' metadata:
+- touch: Update file access time and modification time.
+- rm: Delete files or directories.
+- cp: Replicate files or directories.
+- mv: Move files or directories.
+- rename: Rename files or directories.
+- chmod: Modify permissions on files or directories.
+- chown: Change file or directory owners.
+- chgrp: Change file or directory groups.
+- ln: Create hard links.
+- link: Create hard links.
+- unlink: Delete hard links.
+The atime, ctime, and mtime attributes of a local path (root directory of the mount point) are the current time. So each time the root directory attribute is queried, the current time of the server is returned.
+Procedure
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- 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.
+ - Install the NFS client.
- Install the NFS client.
- Run the following command to check whether the NFS software package is installed.
- In CentOS, Red Hat, Oracle Enterprise Linux, SUSE, EulerOS, Fedora, or OpenSUSE: +
- In Debian or Ubuntu: +
If a command output similar to the following is displayed, the NFS software package has been installed and you can go to 4. If no such command output is displayed, go to b.+- In CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
libnfsidmap +nfs-utils
+ - In SUSE or OpenSUSE:
nfsidmap +nfs-client
+ - In Debian or Ubuntu:
nfs-common
+
- 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.
+
- Run the following command to check whether the NFS software package is installed.
- Install the NFS client.
- 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.example.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.
- 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.)
+ - Run the following command to mount the file system to the ECS in the same VPC as the file system. You can now mount the file system 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,tcp Mount point Local path
+To mount a general purpose file system, run the following command: mount -t nfs -o vers=3,timeo=600,noresvport,nolock,proto=tcp Mount point Local path
++
After a client ECS is restarted, it loses the file system mount information. You can configure auto mount in the fstab file to ensure that the ECS automatically mounts the file system 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.
+noresvport
+Whether the NFS client uses a new TCP port when a network connection is re-established.
+For example, during a network switch, the file system may be blocked, and it may take several minutes to re-establish the connection automatically. In more severe cases, you may need to restart the client ECS. It is strongly recommended that you specify noresvport, which ensures that your file system remains uninterrupted after a network reconnection or recovery.
+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.
+proto
+Protocol used by NFS clients to send requests to the server. Both UDP and TCP protocols can be used.
+General Purpose File System does not support UDP. Therefore, you need to set proto to tcp for general purpose file systems.
+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:/.
+Figure 1 shows an example.
+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
+A local directory on the ECS used to mount the file system, for example, /local_path.
+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. Recommended value: 1
+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.
+noresvport
+Whether the NFS client uses a new TCP port when a network connection is re-established.
+For example, during a network switch, the file system may be blocked, and it may take several minutes to re-establish the connection automatically. In more severe cases, you may need to restart the client ECS. It is strongly recommended that you specify noresvport, which ensures that your file system remains uninterrupted after a network reconnection or recovery.
+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.
+ - 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=)
+ - Check that you can 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.
+
Mounting an NFS File System to ECSs (Windows)
-After creating a file system, you need to mount the file system to servers so that they can share the file system.
+After creating a file system, you need to mount the file system to cloud servers so that they can share the file system.
This section uses Windows Server 2012 as the example OS to describe how to mount an NFS file system. For other versions, perform the steps based on the actual situation.
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 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.
Prerequisites
- You have created a file system and have obtained the mount point of the file system.
- At least one ECS that is in the same VPC as the file system is available.
- The IP address of the DNS server for resolving the file system domain name has been configured on the ECS. For details, see Configuring DNS. SFS Turbo file systems do not require domain name resolution.
Limitations and Constraints
SFS Turbo file systems cannot be mounted to Windows ECSs.
-General purpose file systems cannot be mounted to Windows ECSs.
+Constraints
SFS Turbo file systems cannot be mounted to Windows ECSs.
+General purpose file systems cannot be mounted to Windows servers.
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.
+
Procedure
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- On the ECS console, 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.
- Choose , as shown in Figure 5. -
- Right-click Client for NFS, choose Properties, change the transport protocol to TCP, and select Use hard mounts, as shown in Figure 6 and Figure 7. - +
- 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:
+ - 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 is in the same VPC as the file system to mount the file system.
For SFS Capacity-Oriented file systems: mount -o nolock Mount point X:
- - Free drive letter of the disk: A drive letter that is not in use, such as drive letter E or X.
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.+-You can move the cursor to the mount point and click
+ - next to the mount point to copy it. For details, see Figure 8. If the information shown in Figure 9 is displayed, the mount 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.
- + To distinguish different file systems mounted on an ECS, you can rename file systems by right-clicking a file system and choose Rename.
diff --git a/docs/sfs/umn/sfs_01_0002.html b/docs/sfs/umn/sfs_01_0002.html index f2229fd8a..92250e026 100644 --- a/docs/sfs/umn/sfs_01_0002.html +++ b/docs/sfs/umn/sfs_01_0002.html @@ -6,7 +6,7 @@Troubleshooting
If a file system is mounted to a Linux ECS and a Windows ECS, on the Windows ECS, data cannot be written to the files created by the Linux ECS. To address this problem, modify the registry and change both UID and GID values to 0 for NFS accesses from Windows. 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.
+
Troubleshooting
If a file system is mounted to a Linux ECS and a Windows ECS, on the Windows ECS, you cannot write data to the files created by the Linux ECS. To address this problem, modify the registry and change both UID and GID values to 0 for NFS accesses from Windows. 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.
Figure 1 shows the relationship between regions and AZs.
diff --git a/docs/sfs/umn/sfs_01_0005.html b/docs/sfs/umn/sfs_01_0005.html index c5ae64761..8e87a6c9a 100644 --- a/docs/sfs/umn/sfs_01_0005.html +++ b/docs/sfs/umn/sfs_01_0005.html @@ -36,7 +36,7 @@Selecting a Region
Select a region closest to your target users for lower network latency and quick access.
+Selecting a Region
You are advised to select a region close to you or your target users. This helps ensure low access latency.
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
SFS Turbo
Expandable to 32 TB, SFS Turbo provides fully hosted shared file storage. It features high availability and durability to support massive small files and applications requiring low latency and high IOPS. SFS Turbo is perfect to scenarios such as high-performance websites, log storage, compression and decompression, DevOps, enterprise offices, and container applications.
-- High-performance websites
For I/O-intensive website services, SFS Turbo can provide shared website source code directories for multiple web servers, enabling low-latency and high-IOPS concurrent share access.
+- High-performance websites
For I/O-intensive website services, SFS Turbo can provide shared website source code directories for multiple web servers, enabling low-latency and high-IOPS concurrent shared access.
- Log storage
SFS Turbo can provide multiple service nodes for shared log output directories, facilitating log collection and management of distributed applications.
+- Log storage
SFS Turbo can provide shared log output directories for multiple service nodes, facilitating log collection and management of distributed applications.
- Log storage
- High-performance websites
Large capacity, high bandwidth, and low cost
Application Scenarios
+Application scenarios
Cost-sensitive workloads which require large-capacity scalability, such as media processing, file sharing, HPC, and data backup. For workloads dealing with massive small files, SFS Turbo is recommended.
Large capacity, high bandwidth, and low cost
Application Scenarios
+Application scenarios
Cost-sensitive workloads which require large-capacity scalability, such as media processing, file sharing, high-performance computing, and data backup. For workloads dealing with massive small files, SFS Turbo is recommended.
SFS Turbo
-Table 3 SFS Turbo file systems Parameter
20 MB/s/TiB
+20 MB/s/TiB
40 MB/s/TiB
+40 MB/s/TiB
125 MB/s/TiB
+125 MB/s/TiB
250 MB/s/TiB
1 million
Single-queue, 4 KB latency
+Single-queue, 4 KiB latency
2–5 ms
Table 4 Previous-generation SFS Turbo file systems Parameter
+Table 4 Previous-generation SFS Turbo file systems Parameter
Standard
+Standard
Standard-Enhanced
+Standard-Enhanced
Performance
+Performance
Performance-Enhanced
+Performance-Enhanced
Max. bandwidth
@@ -213,7 +213,7 @@100,000
Single-queue, 4 KB latency
+Single-queue, 4 KiB latency
2–5 ms
File System Encryption
-SFS provides you with the encryption function. You can encrypt data on the new file systems if needed.
-Keys for encrypting file systems are provided by Key Management Service (KMS), which is secure and convenient. You do not need to establish and maintain key management infrastructure. If you want to use your own key material, use the key import function on the KMS console to create a custom key whose key material is empty and import the key material to the custom key. For details, see section "Importing Key Materials" in Key Management Service User Guide.
+SFS provides you with the encryption function. You can encrypt data on newly created file systems if needed.
+Keys for encrypting file systems are provided by Key Management Service (KMS), which is secure and convenient. You do not need to establish and maintain key management infrastructure. If you want to use your own key material, use the key import function on the KMS console to create a custom key whose key material is empty and import the key material to the custom key. For details, see section "Importing Key Materials" in Key Management Service User Guide.
To use the file system encryption function, you need to authorize SFS Capacity-Oriented to access KMS when creating an SFS Capacity-Oriented file system. SFS Turbo file systems do not need authorization.
Encryption Key
Keys provided by KMS for encrypting SFS Capacity-Oriented file systems include a default key and custom keys.
- Default key: SFS automatically creates a default key and names it sfs/default.
The default key cannot be disabled and does not support scheduled deletion.
diff --git a/docs/sfs/umn/sfs_01_0007.html b/docs/sfs/umn/sfs_01_0007.html index bfc91baf6..fd6b7adc2 100644 --- a/docs/sfs/umn/sfs_01_0007.html +++ b/docs/sfs/umn/sfs_01_0007.html @@ -14,12 +14,12 @@Elastic Cloud Server (ECS)
+
VPC provisions an isolated virtual network environment defined and managed by yourself, improving the security of cloud resources and simplifying network deployment.
-A server cannot access file systems in a different VPC. Before using SFS, assign the file system and the servers to the same VPC.
+A VPC enables you to provision logically isolated, configurable, and manageable virtual networks for ECSs, improving the security of cloud resources and simplifying network deployment.
+A server cannot access file systems in a different VPC. Before using SFS, ensure that the file system and the servers are in the same VPC.
Virtual Private Cloud (VPC)
-SFS Capacity-Oriented
- SFS Capacity-Oriented can be accessed only on the intranet and used only on the cloud.
- Only NFSv3 is supported (NFSv4 is not supported).
- A maximum of 10,000 compute nodes can be mounted to and access a single file system at the same time.
- The maximum capacity of a single file system is 2 PB, and that of a single file is 240 TB.
- Multi-VPC access is supported. You can add a maximum of 20 VPCs for one file system and create a maximum of 400 ACL rules for all added VPCs.
General Purpose File System
- Only the NFSv3 protocol is supported (NFSv4 is not supported).
- General purpose file systems do not support file system encryption.
- General purpose file systems can only be accessed over the intranet.
- A single directory can contain a maximum of 30 million files.
- General purpose file systems cannot be mounted to 32-bit Linux ECSs.
- The name of a general purpose file system must be globally unique. It cannot be the same as any existing general purpose file system name or one created by any other user. And it cannot be changed after the file system is created.
- If a general purpose file system is deleted, you can create a new file system with the same name as the deleted one 30 minutes after that file system has been deleted.
- General purpose file systems cannot be mounted to Windows ECSs.
- Root directory permissions of general purpose file systems cannot be changed.
- When General Purpose File System is used as the storage backend of CCE or CCI, you need to empty the in-use file systems before deleting any PVCs or PVs. If you directly delete the PVCs or PVs, the file systems may fail to be deleted. Check whether the file systems are deleted on the General Purpose File System console.
Deleting PVCs or PVs takes some time. The billing ends until the corresponding file systems are deleted from the General Purpose File System console.
+-General Purpose File System
- Only the NFSv3 protocol is supported (NFSv4 is not supported).
- General purpose file systems do not support file system encryption.
- General purpose file systems can only be accessed over the intranet.
- A single directory can contain a maximum of 30 million files.
- General purpose file systems cannot be mounted to 32-bit Linux servers.
- The name of a general purpose file system must be globally unique. It cannot be the same as the name of any existing general purpose file system or one created by any other user. And it cannot be changed after the file system is created.
- If a general purpose file system is deleted, you can only create a general purpose file system with the same name as the deleted one 30 minutes after that file system has been deleted.
- General purpose file systems cannot be mounted to Windows servers.
- General purpose file systems' root directory permissions cannot be changed.
- When general purpose file systems are used as the storage backend of CCE or CCI, you need to empty the file systems before you can delete any PVCs or PVs. If you directly delete the PVCs or PVs, the file systems may fail to be deleted. Check whether the file systems are deleted on the General Purpose File System console.
Deleting PVCs or PVs takes some time. The billing ends until the corresponding general purpose file systems are deleted.
SFS Turbo
- Only the NFSv3 protocol is supported (NFSv4 is not supported).
- A maximum of 500 compute nodes can be mounted to and access a single file system at the same time.
- The maximum capacity of a single file system is 32 TB, and the maximum size of a single file allowed is 320 TB.
- Maximum number of files supported by a single file system = Capacity/16. For example, the maximum number of files supported by a 500 GB file system is 32,768,000 (500 GB/16 KB = 500 x 1024 x 1024/16).
- By default, a single directory can contain a maximum of 20 million files.
If you need to execute the ls, du, cp, chmod, or chown command on a directory, you are advised to place no more than 500,000 files or subdirectories in that directory. Otherwise, requests may take long times as the NFS protocol sends a large number of requests to traverse directory files and requests are queueing up.
+diff --git a/docs/sfs/umn/sfs_01_0013.html b/docs/sfs/umn/sfs_01_0013.html index a02ee326d..e073c26dd 100644 --- a/docs/sfs/umn/sfs_01_0013.html +++ b/docs/sfs/umn/sfs_01_0013.html @@ -31,7 +31,7 @@SFS Turbo
- Only the NFSv3 protocol is supported (NFSv4 is not supported).
- A maximum of 500 compute nodes can be mounted to and access a single file system at the same time.
- The maximum capacity of a single file system is 32 TB, and the maximum size of a single file allowed is 320 TB.
- Maximum number of files supported by a single file system = Capacity/16. For example, the maximum number of files supported by a 500 GB file system is 32,768,000 (500 GB/16 KB = 500 x 1024 x 1024/16).
- By default, a single directory can contain a maximum of 20 million files.
If you need to execute the ls, du, cp, chmod, or chown command on a directory, you are advised to place no more than 500,000 files or subdirectories in that directory. Otherwise, requests may take long times as the NFS protocol sends a large number of requests to traverse directory files and requests are queuing up.
- The maximum full path is 4,096 bytes, and the maximum file name length is 255 bytes.
- The maximum soft link length is 1,024 bytes.
- The maximum number of hard links is 255.
- The maximum directory depth is 100 layers.
SFS Turbo ReadOnlyAccess
Read-only permissions for SFS Turbo. Users granted these permissions can only view SFS Turbo file system data.
+Read-only permissions for SFS Turbo. Users with these permissions can only view SFS Turbo file system data.
System-defined policy
-
-
- 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 7108f2ade..c73661ade 100644
--- a/docs/sfs/umn/sfs_01_0025.html
+++ b/docs/sfs/umn/sfs_01_0025.html
@@ -1,19 +1,19 @@
- 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.
@@ -27,17 +27,17 @@Procedure (Linux)
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- Log in to the ECS as user root.
- Run the vi /etc/fstab command to edit the /etc/fstab file.At the end of the file, add the file system information, for example:
Mount point /local_path nfs vers=3,timeo=600,nolock 0 0
Replace Mount point and /local_path with actual values. You can obtain the mount point from the Mount Address column of the file system. Each record in the /etc/fstab file corresponds to a mount. Each record has six fields, as described in Field Description.
- For optimal system performance, configure file system information based on the previous example configuration. If needed, you can customize part of mount parameters. However, the customization may affect system performance.
- Press Esc, input :wq, and press Enter to save and exit.
After the preceding configurations are complete, the system reads mounting information from the /etc/fstab file to automatically mount the file system when the ECS restarts.
+ - Press Esc, input :wq, and press Enter to save and exit.
After the preceding configurations are complete, the system reads mount information from the /etc/fstab file to automatically mount the file system when the ECS restarts.
- (Optional) Run the following command to view the updated content of the /etc/fstab file:
cat /etc/fstab
Figure 1 shows the updated file content.
- + - If auto mount fails due to a network issue, add the sleep option and a time in front of the mount command in the rc.local file, and mount the file system after the NFS service is started.
sleep 10s && sudo mount -t nfs -o vers=3,timeo=600,noresvport,nolock,tcp Mount point/local_path
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).
+The mount point of the file system to be mounted. Set it to the mount point in the mount command 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).
+A directory created on the ECS used to mount the file system. Set it to the local path in the mount command in Mounting an NFS File System to ECSs (Linux).
nfs
Mount type, that is, file system or partition type. Set it to nfs.
+The file system or partition mount type. Set it to nfs.
vers=3,timeo=600,nolock
@@ -63,16 +63,16 @@Procedure (Windows)
Ensure that an NFS client has been installed on the target server before mounting. This section uses Windows Server 2012 as an example to describe how to mount a file system.
-- 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.
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- Log in to the ECS.
- Before mounting the file system, create a script named auto_mount.bat, save the script to a local host, and record the save path. The script contains the following content:
mount -o nolock mount point corresponding drive letter
-Figure 2 Saving the script+
Figure 2 Saving the scriptFor example, the auto_mount.bat script of a file system contains the following content:
-For SFS Capacity-Oriented file systems: mount -o nolock mount point X:
+For SFS Capacity-Oriented file systems: mount -o nolock Mount point X:
- You can copy the mount command of the file system from the console.
- After the script is created, manually run the script in the Command Prompt to ensure that the script can be executed successfully. If you can view the file system in This PC after the script execution, the script can be executed properly.
- This .bat script cannot be stored in the same path in 4 that stores the .vbs file. In this example, the .bat script is stored in C:\test\.
- Create a .txt file whose name is XXX.vbs and save the file to the directory C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The file contains the following content:
set ws=WScript.CreateObject("WScript.Shell") ws.Run "Local path and script name of the auto_mount.bat script /start", 0-Figure 3 Creating .vbs file+
Figure 3 Creating .vbs file In this example, the local path of the auto_mount.bat script is C:\test\. Therefore, the content in the .vbs file is as follows:
set ws=WScript.CreateObject("WScript.Shell") ws.Run "C:\test\auto_mount.bat /start",0diff --git a/docs/sfs/umn/sfs_01_0026.html b/docs/sfs/umn/sfs_01_0026.html index fdf06abdd..9734f6351 100644 --- a/docs/sfs/umn/sfs_01_0026.html +++ b/docs/sfs/umn/sfs_01_0026.html @@ -4,15 +4,15 @@If a file system is no longer used and needs to be deleted, you are advised to unmount the file system and then delete it.
-Prerequisites
Before unmounting a file system, stop the process and read/write operations.
Linux OS
- 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 go to the ECS console.
-Linux OS
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- Log in to the ECS.
- Run the following command:
umount Local path
Local path: An ECS local directory where the file system is mounted, for example, /local_path.
Before running the umount command, stop all read and write operations related to the file system and exit from the local path. Or, the unmounting will fail.
diff --git a/docs/sfs/umn/sfs_01_0027.html b/docs/sfs/umn/sfs_01_0027.html index 9ec7daf10..1ebc95049 100644 --- a/docs/sfs/umn/sfs_01_0027.html +++ b/docs/sfs/umn/sfs_01_0027.html @@ -4,30 +4,30 @@Windows OS
- 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 go to the ECS console.
- Log in to the ECS.
- Right-click the file system to be unmounted and choose Disconnect.Figure 1 Unmounting+
Windows OS
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Compute > Elastic Cloud Server to go to the ECS console.
- Log in to the ECS.
- Right-click the file system to be unmounted and choose Disconnect.Figure 1 Unmounting
- If the file system disappears from the network location, it has been unmounted.
- Log in to the management console using a cloud account.
This section explains how to enable or add a software repository in CentOS, SUSE, and Ubuntu.
CentOS
- Run the following command to check whether a software repository has been enabled.
yum repolist all
If status is disabled, as shown in Figure 1, no software repository has been enabled. Proceed to the next step.
- + - Run the following command to enable a software repository. This step uses Public-OTC-CentOS-7-Base as an example.
yum-config-manager --enable Public-OTC-CentOS-7-Base
-Figure 2 Enabling a software repository+
Figure 2 Enabling a software repository - Run the following command to check whether the software repository described in step 2 has been enabled.
yum repolist all
-If status is enabled, as shown in Figure 3, the software repository has been enabled. +If status is enabled, as shown in Figure 3, the software repository has been enabled.SUSE
- Run the following command to check whether a software repository has been enabled.
zypper lr
If no software repository is detected, as shown in Figure 4, proceed to the next step.
- - - Run the following command to add a software repository. This step uses opensuse12.2 as an example.zypper addrepo http://download.opensuse.org/distribution/12.2/repo/oss/ opensuse-mainFigure 5 Adding a software repository+ +
- Run the following command to add a software repository. This step uses opensuse12.2 as an example.
zypper addrepo http://download.opensuse.org/distribution/12.2/repo/oss/ opensuse-mainFigure 5 Adding a software repository- Run the following command to update and add software repositories.
zypper refresh
-Figure 6 Updating and adding repositories+
Figure 6 Updating and adding repositories- Run the following command to check whether the software repository described in step 2 has been enabled.
zypper lr
-If Enabled is Yes, as shown in Figure 7, the software repository has been enabled. +-If Enabled is Yes, as shown in Figure 7, the software repository has been enabled.Ubuntu
- Run the following command to add a software repository.apt-add-repository http://archive.canonical.com/ubuntudiff --git a/docs/sfs/umn/sfs_01_0032.html b/docs/sfs/umn/sfs_01_0032.html index c19a2022a..cde2c01d0 100644 --- a/docs/sfs/umn/sfs_01_0032.html +++ b/docs/sfs/umn/sfs_01_0032.html @@ -4,12 +4,12 @@Figure 8 Adding a software repository+
Ubuntu
- Run the following command to add a software repository.apt-add-repository http://archive.canonical.com/ubuntuFigure 8 Adding a software repository
- Run the following command to update and add software repositories.
apt-get update
-Figure 9 Updating and adding repositories+
Figure 9 Updating and adding repositories
This chapter describes how to use IAM to implement fine-grained permissions control for your SFS resources. With IAM, you can:
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing SFS resources.
- Grant only the permissions required for users to perform a specific task.
If your cloud account does not require individual IAM users, skip this section.
-This section describes the procedure for granting permissions (see Figure 1).
+This section describes the procedure for granting permissions (see Figure 1).
-Prerequisites
Learn about the permissions (see Permissions) supported by SFS and choose policies or roles according to your requirements.
Restrictions
- Both system-defined policies and custom policies are supported in SFS Turbo file systems.
-Constraints
- Both system-defined policies and custom policies are supported in SFS Turbo file systems.
+ + \ No newline at end of file diff --git a/docs/sfs/umn/sfs_01_0033.html b/docs/sfs/umn/sfs_01_0033.html index 77f3a54fb..88fdf71be 100644 --- a/docs/sfs/umn/sfs_01_0033.html +++ b/docs/sfs/umn/sfs_01_0033.html @@ -1,7 +1,7 @@Process Flow
+Process Flow
- Create a user group and assign permissions to it.
Create a user group on the IAM console, and attach the SFS Turbo ReadOnlyAccess policy to the group.
- Create a user and add it to a user group.
Create a user on the IAM console and add the user to the group created in 1.
- Log in and verify permissions.
Log in to the SFS console using the created user, and verify that the user only has read permissions for SFS.
@@ -23,3 +23,10 @@
Creating a Custom Policy
-Custom policies can be created to supplement the system-defined policies of SFS. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in the Scalable File Service API Reference.
+Custom policies can be created to supplement the system-defined policies of SFS. For the actions supported for custom policies, see section "Permissions Policies and Supported Actions" in the Scalable File Service API Reference.
You can create custom policies in either of the following two ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
This section provides examples of common custom SFS policies.
diff --git a/docs/sfs/umn/sfs_01_0036.html b/docs/sfs/umn/sfs_01_0036.html index 9c5d3703f..47d0d73c2 100644 --- a/docs/sfs/umn/sfs_01_0036.html +++ b/docs/sfs/umn/sfs_01_0036.html @@ -1,16 +1,16 @@Configuring Multi-VPC Access
-VPC provisions an isolated virtual network environment defined and managed by yourself, improving the security of cloud resources and simplifying network deployment. When using SFS, a file system and the associated ECSs need to belong to the same VPC for file sharing.
+A VPC enables you to provision logically isolated, configurable, and manageable virtual networks for ECSs, improving the security of cloud resources and simplifying network deployment. When using SFS to share files, a file system and the ECSs need to be in the same VPC.
In addition, VPC can use network access control lists (ACLs) to implement access control. A network ACL is an access control policy system for one or more subnets. Based on inbound and outbound rules, it determines whether data packets are allowed in or out of any associated subnet. In the VPC list of a file system, each time an authorized address is added and corresponding permissions are set, a network ACL is created.
For more information about VPC, see the Virtual Private Cloud User Guide.
-Scenarios
Multi-VPC access can be configured for an SFS Capacity-Oriented or a general purpose file system so that ECSs in different VPCs can share the same file system, as long as the VPCs that the ECSs belong to are added as authorized VPCs of the file system or the ECS IP addresses are added as authorized IP addresses of the VPCs.
-This section describes how to configure multi-VPC access for an SFS Capacity-Oriented or a general purpose file system.
+-Scenarios
You can configure multiple VPCs for an SFS Capacity-Oriented or general purpose file system so that ECSs in different VPCs can share the same file system, as long as the VPCs are added as authorized VPCs or the ECS IP addresses are added as authorized IP addresses of the VPC.
+This section describes how to configure multi-VPC access for an SFS Capacity-Oriented, or a general purpose file system.
Restrictions
- You can add a maximum of 20 VPCs for each file system. A maximum of 400 ACL rules for added VPCs can be created. When adding a VPC, the default IP address 0.0.0.0/0 is automatically added.
- If a VPC added to a file system has been deleted from the VPC console, the IP addresses or IP address ranges of this VPC can still be seen as activated in the file system's VPC list. But this VPC can no longer be used and you are advised to delete it from the list.
- You need to configure a VPC endpoint for each VPC you want to create the general purpose file system. Or, the file system will fail to be mounted.
-Constraints
- You can add a maximum of 20 VPCs for each file system. A maximum of 400 ACL rules for added VPCs can be created. When adding a VPC, the default IP address 0.0.0.0/0 is automatically added.
- If a VPC added to a file system has been deleted from the VPC console, the IP addresses or IP address ranges of this VPC can still be seen as active in the file system's VPC list. But this VPC can no longer be used and you are advised to delete it from the list.
- You need to configure a VPC endpoint for each VPC you want to add as an authorized VPC of a general purpose file system. Or, the file system will fail to be mounted.
Procedure for SFS Capacity-Oriented
- Log in to the SFS console.
- In the file system list, click the name of the target file system. On the displayed page, locate the Authorizations area.
- If no VPCs are available, create one. You can add multiple VPCs for a file system. Click Add Authorized VPC and the Add Authorized VPC dialog box is displayed. See Figure 1.
You can select multiple VPCs from the drop-down list.
- +Procedure for SFS Capacity-Oriented
- Log in to the SFS console.
- In the file system list, click the name of the target file system. On the displayed page, locate the Authorizations area.
- If no VPCs are available, create one. You can add multiple VPCs for a file system. Click Add Authorized VPC to open the Add Authorized VPC dialog box, as shown in Figure 1.
You can select multiple VPCs from the drop-down list.
+ - Click OK. A successfully added VPC is displayed in the list. When adding a VPC, the default IP address 0.0.0.0/0 is automatically added. The default read/write permission is Read-write, the default user permission is no_all_squash, and the default root permission is no_root_squash.
- View the VPC information in the VPC list. For details about the parameters, see Table 1.
- - Click
on the left of the VPC name to view details about the IP addresses/segments added to this VPC. You can add, edit, or delete IP addresses/segments. In the Operation column of the target VPC, click Add. The Add Authorized Address/Segment dialog box is displayed. See Figure 2. Table 2 describes the parameters to be configured.
+ - Click on the left of the VPC name to view details about the IP addresses/segments added to this VPC. You can add, edit, or delete IP addresses/segments. In the Operation column of the target VPC, click Add. The Add Authorized Address/Segment dialog box is displayed, as shown in Figure 2. Table 2 describes the parameters to be configured.
-
Table 2 Parameter description Parameter
Authorized Address/Segment
- Enter one IPv4 address or address segment at a time.
- The entered IPv4 address or address segment must be valid and cannot be one starting with 0 except 0.0.0.0/0. If you add 0.0.0.0/0, any IP address within this VPC will be authorized for accessing the file system. Class D and class E IP addresses are not supported. Therefore, do not enter an IP address or address segment starting with any number ranging from 224 to 255, for example 224.0.0.1 or 255.255.255.255. IP addresses or address segments starting with 127 are also not supported. If an invalid IP address or address segment is used, the access rule may fail to be added or the added access rule cannot take effect.
- Do not enter multiple IP addresses (separated using commas) at a time. For example, do not enter 10.0.1.32,10.5.5.10.
- If you enter an IP address segment, enter it in the format of IP address/mask. For example, enter 192.168.1.0/24. Do not enter in the format of 192.168.1.0-255 or 192.168.1.0-192.168.1.255. The number of bits in a subnet mask must be an integer ranging from 0 to 31, and mask value 0 is valid only in 0.0.0.0/0.
- Enter one IPv4 address or range in each line.
- Enter a valid IPv4 address or range that is not starting with 0 except 0.0.0.0/0. If you add 0.0.0.0/0, any IP address within this VPC will be authorized to access the file system. Do not enter an IP address or IP address range starting with any number ranging from 224 to 255, for example 224.0.0.1 or 255.255.255.255, because class D and class E IP addresses are not supported. IP addresses starting with 127 are also not supported. If you enter an invalid IP address or IP address range, the permission rule may fail to be added, or the authorization will not work.
- Do not enter multiple IP addresses (separated using commas) at a time. For example, do not enter 10.0.1.32,10.5.5.10.
- If you enter an IP address range, enter it in the format of IP address/mask. For example, enter 192.168.1.0/24. Do not use the following format:192.168.1.0-255 or 192.168.1.0-192.168.1.255. The number of bits in a subnet mask must be an integer ranging from 0 to 31, and mask value 0 is valid only in 0.0.0.0/0.
Read-Write Permission
@@ -75,11 +75,11 @@ -For an ECS in VPC A, its IP address can be added to the authorized IP address list of VPC B, but the file system of VPC B cannot be mounted to this ECS. The VPC of the ECS and the file system must be the same.
+ For an ECS in VPC A, its IP address can be added as an authorized IP address of VPC B, but the file system in VPC B cannot be mounted to this ECS. The VPC used by the ECS and the file system must be the same.
Procedure for General Purpose File System
- Log in to the SFS console.
- In the file system list, click the name of the target file system. On the displayed page, locate the permissions list.
- If no VPCs are available, create one. Click Add VPC. Table 3 describes the parameters.Figure 3 Add VPC+
Procedure for General Purpose File System
- Log in to the SFS console.
- In the file system list, click the name of the target file system. On the displayed page, locate the permissions list.
- If no VPCs are available, create one. Click Add VPC. Table 3 describes the parameters.Figure 3 Add VPC
Table 3 Parameter description Parameter
Authorizations
The value can be Read/Write or Read-only. The default value is Read/Write.
+The value can be Read/Write or Read-only. The default value is Read/Write.
- Click OK. The added VPC will be displayed in the list.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
-Figure 4 Create VPC Endpoint+
Figure 4 Create VPC Endpoint- Set the parameters as prompted.
Table 4 Parameters for purchasing an endpoint Parameter
VPC endpoint tags. Each tag consists of a key and a value.
Tag keys and values must meet the requirements listed in Table 5.
NOTE:If a predefined tag has been created in TMS, you can select the corresponding tag key and value.
-For details about predefined tags, see section "Predefined Tag Overview" in the Tag Management Service User Guide.
+For details about predefined tags, see section "Predefined Tag Overview" in the Tag Management Service User Guide.
Configuring DNS
A DNS server is used to resolve domain names of file systems. The DNS server IP address is 100.125.4.25.
-Scenarios
By default, the IP address of the DNS server used to resolve domain names of file systems is automatically configured on ECSs when creating ECSs. No manual configuration is needed except when the resolution fails due to a change in the DNS server IP address.
+-Scenarios
By default, the IP address of the DNS server used to resolve domain names of file systems is automatically configured on ECSs when they are created. No manual configuration is needed except when the resolution fails due to a change in the DNS server IP address.
Windows Server 2012 is used as an example in the operation procedures for Windows.
Procedure (Linux)
- Log in to the ECS as user root.
- Run the vi /etc/resolv.conf command to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. See Figure 1.
+
Procedure (Linux)
- Log in to the ECS as user root.
- Run the vi /etc/resolv.conf command to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. See Figure 1.
The format is as follows:
nameserver 100.125.4.25
- Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
- Run the following command to check whether the IP address is successfully added:
cat /etc/resolv.conf
- Run the following command to check whether an IP address can be resolved from the file system domain name:
nslookup File system domain name
- Obtain the file system domain name from the file system mount point.
- (Optional) In a network environment of the DHCP server, edit the /etc/resolv.conf file to prevent the file from being automatically modified upon an ECS startup, and prevent the DNS server IP address added in 2 from being reset.
- Run the following command to lock the file:chattr +i /etc/resolv.conf -
Run the chattr -i /etc/resolv.conf command to unlock the file if needed.
+- (Optional) In a network environment that uses the DHCP server, edit the /etc/resolv.conf file to prevent the file from being automatically modified upon an ECS restart, and prevent the DNS server IP address added in 2 from being reset.
- Run the following command to lock the file:
- Run the following command to check whether the editing is successful:
If the information shown in Figure 2 is displayed, the file is locked.
- +
diff --git a/docs/sfs/umn/sfs_01_0039.html b/docs/sfs/umn/sfs_01_0039.html index 4f2a05775..a276a6310 100644 --- a/docs/sfs/umn/sfs_01_0039.html +++ b/docs/sfs/umn/sfs_01_0039.html @@ -3,9 +3,9 @@Procedure (Windows)
- Go to the ECS console and log in to the ECS running Windows Server 2012.
- Click This PC in the lower left corner.
- On the page that is displayed, right-click Network and choose Properties from the drop-down list. The Network and Sharing Center page is displayed, as shown in Figure 3. Click Local Area Connection. -
- In the Activity area, select Properties. See Figure 4. -
- In the Local Area Connection Properties dialog box that is displayed, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. See Figure 5. -
- In the dialog box that is displayed, select Use the following DNS server addresses: and configure DNS, as shown in Figure 6. The DNS server IP address is 100.125.4.25. After completing the configuration, click OK.
+
Procedure (Windows)
- Go to the ECS console and log in to the ECS running Windows Server 2012.
- Click This PC in the lower left corner.
- On the page that is displayed, right-click Network and choose Properties from the drop-down list. The Network and Sharing Center page is displayed, as shown in Figure 3. Click Local Area Connection. +
- In the Activity area, select Properties. See Figure 4. +
- In the Local Area Connection Properties dialog box that is displayed, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. See Figure 5. +
- In the dialog box that is displayed, select Use the following DNS server addresses: and configure DNS, as shown in Figure 6. The DNS server IP address is 100.125.4.25. After completing the configuration, click OK.
File System Resizing
-Scenarios
You can expand or shrink the capacity of a file system when needed.
Constraints
SFS Turbo file systems can only have their capacities expanded, not reduced. And only In-use file systems can be expanded.
-SFS Capacity-Oriented file systems support resizing, during which services are not affected. Only In-use file systems can be expanded.
-SFS Turbo file systems support online capacity expansion, during which mounting a file system may fail and the connection being used for mounting will experience about a 30-second (max. 3 minutes) I/O delay. So you are advised to expand capacity during off-peak hours. Note that only In-use file systems can be expanded.
+Constraints
SFS Turbo file systems can only have their capacities expanded, not reduced. And only in-use file systems can be expanded.
+SFS Capacity-Oriented file systems support resizing, during which services are not affected. Only in-use file systems can be expanded.
+SFS Turbo file systems support online capacity expansion, during which mounting a file system may fail and the connection being used for mounting will experience about a 30-second (max. 3 minutes) I/O delay. So you are advised to expand capacity during off-peak hours. Note that only in-use file systems can be expanded.
General purpose file systems have no capacity limit and do not support resizing.
-Precautions
The rules for resizing an SFS Capacity-Oriented file system are as follows:
@@ -15,8 +15,8 @@Procedure
- Log in to the SFS console.
- In the file system list, click Resize or Expand Capacity in the row of the desired file system. The following dialog box is displayed Figure 1 Resizing an SFS Capacity-Oriented file system-
Figure 2 Expanding an SFS Turbo file system+
Procedure
- Log in to the SFS console.
- In the file system list, click Resize or Expand Capacity in the row of the desired file system. A dialog box is displayed. Figure 1 Resizing an SFS Capacity-Oriented file system+Figure 2 Expanding an SFS Turbo file system
- Enter a new capacity and click OK. The following tables describe the parameters.
Table 1 SFS Capacity-Oriented file system resizing parameters Parameter
New Capacity
New storage capacity of the file system
-Value constraints:- For a Standard, Standard-Enhanced, Performance, or Performance-Enhanced file system, the minimum expansion increment is 100 GB. A Standard or Performance file system can be expanded to up to 32 TB, and a Standard - Enhanced or Performance - Enhanced file system can be expanded to up to 320 TB.
- For a 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file system, the expansion increment is 1.2 TB, and a file system can be expanded to up to 1 PB.
Value constraints:- For a Standard, Standard-Enhanced, Performance, or Performance-Enhanced file system, the minimum expansion increment is 100 GB. A Standard or Performance file system can be expanded to up to 32 TB, and a Standard-Enhanced or Performance-Enhanced file system can be expanded to up to 320 TB.
- For a 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file system, the expansion increment is 1.2 TB, and the increment must be an integer multiple of 1.2 TB. The new capacity can be no more than 1 PB.
Encryption
Creating an Encrypted File System
To use the file system encryption function, you need to authorize SFS Capacity-Oriented to access KMS when creating an SFS Capacity-Oriented file system. If you have the Security Administrator rights, grant SFS the permissions to access KMS directly. Otherwise, you need to contact the system administrator to obtain the "Security Administrator" rights first. For details, see File System Encryption.
SFS Turbo file systems do not require authorization.
-You can create an encrypted or non-encrypted file system, but you cannot change the encryption settings of an existing file system.
+You can create a file system that is encrypted or not, but you cannot change the encryption attribute of an existing file system.
For details about how to create an encrypted file system, see Create a File System.
Unmounting an Encrypted File System
If the custom key used by the encrypted file system is disabled or scheduled for deletion, the file system can only be used within a certain period of time (30s by default). Exercise caution in this case.
-For details about how to unmount a file system, see Unmount a File System
+For details about how to unmount the file system, see Unmount a File System.
diff --git a/docs/sfs/umn/sfs_01_0043.html b/docs/sfs/umn/sfs_01_0043.html index 7018f5dbc..d072be5ec 100644 --- a/docs/sfs/umn/sfs_01_0043.html +++ b/docs/sfs/umn/sfs_01_0043.html @@ -1,12 +1,14 @@Tags
-This section describes how to add tags to existing file systems. You can also add tags when creating file systems. For details, see section Create a File System.
+This section describes how to add tags to existing file systems. You can also add tags when creating file systems. For details, see Create 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 must start with a letter and can only contain letters, digits, hyphens (-), underscores (_), and at signs (@).
- A tag value can contain a maximum of 43 characters and can be an empty string. It must start with a letter and can only contain letters, digits, hyphens (-), underscores (_), and at signs (@).
- You can add a maximum of 20 tags to a 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
- Log in to the SFS console.
- 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. -
- Click the Tags tab.
- On the Tags tab page, click Edit Tag to open the Edit Tag dialog box.
- Add the key and value of the tag and click OK.
- Key: This parameter is mandatory.
- Value: This parameter is optional.
- Tags are composed of key-value pairs.
- A tag key can contain a maximum of 128 characters and cannot be left blank. For a general purpose file system, a tag key can contain letters, digits, spaces, and special characters (_.:=+-@), but it cannot start or end with a space or start with _sys_. For an SFS Turbo file system, a tag key can contain only letters, digits, hyphens (-), underscores (_), and at signs (@).
- A tag value can contain a maximum of 255 characters and can be an empty string. For a general purpose file system, a tag value can contain letters, digits, spaces, and special characters (_.:/=+-@), but it cannot start or end with a space. For an SFS Turbo file system, a tag value can contain only letters, digits, hyphens (-), and underscores (_).
- You can add a maximum of 20 tags to a file system.
- Tag keys of the same file system must be unique.
- After adding a tag to a file system, you can edit the tag key and value, or delete the tag.
diff --git a/docs/sfs/umn/sfs_01_0044.html b/docs/sfs/umn/sfs_01_0044.html index df7ca9f41..6b1b16a92 100644 --- a/docs/sfs/umn/sfs_01_0044.html +++ b/docs/sfs/umn/sfs_01_0044.html @@ -1,9 +1,9 @@Procedure
- Log in to the SFS console.
- In the file system list, find the file system to which you want to add tags and click its name to go to its details page.Figure 1 Tags of a general purpose file system+
Figure 2 Tags of an SFS Turbo file system+
- Click the Tags tab.
- On the Tags tab, click Edit Tag.
The Edit Tag dialog box is displayed.
+ - 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.
Backup
-You can only back up SFS Turbo file systems using CBR while you cannot back up SFS Capacity-Oriented and general purpose file systems.
-Scenarios
A backup is a complete copy of an SFS Turbo file system at a specific time and it records all configuration data and service data at that time.
-For example, if a file system is faulty or encounters a logical error (for example, mis-deletion, hacker attacks, and virus infection), you can use data backups to restore data quickly.
+You can only back up SFS Turbo file systems using CBR but you cannot back up SFS Capacity-Oriented and general purpose file systems.
+Scenarios
A backup is a complete copy of an SFS Turbo file system at a specific time and it records all configuration data and service data at that time.
+For example, if a file system is faulty or encounters a logical error (like accidental deletion, hacker attack, or virus infection), you can use data backups to restore data quickly.
Creating a File System Backup
Ensure that the target file system is available. Or, the backup task cannot start. This procedure describes how to manually create a file system backup.
If any modification is made to a file system during the backup, inconsistencies may occur. For example, there may be duplicate or deleted data, or data discrepancies. Such a modification includes a write, rename, move or delete. To ensure backup data consistency, you are advised to stop the applications or programs that use the file system during the backup, or schedule the backup at off-peak hours.
@@ -13,10 +13,10 @@Using a Backup to Create a File System
In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Data on the new file system is the same as that in the backup.
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your desired region and project. - Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
- Click the Backups tab and locate the desired backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1.
-diff --git a/docs/sfs/umn/sfs_01_0047.html b/docs/sfs/umn/sfs_01_0047.html index ef68f3f6d..b14cf6875 100644 --- a/docs/sfs/umn/sfs_01_0047.html +++ b/docs/sfs/umn/sfs_01_0047.html @@ -2,121 +2,148 @@
- For detailed parameter descriptions, see table "Parameter description" under Table 3.
- Click the Backups tab and locate the desired backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1. + -
- Click Next.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
+- Click Create Now.
- Go back to the file system list and check whether the file system is successfully created.
You will see the file system status change as follows: Creating, Available, Restoring, Available. You may not notice the Restoring status because Instant Restore is supported and the restoration speed is very fast. After the file system status has changed from Creating to Available, the file system is successfully created. After the status has changed from Restoring to Available, backup data has been successfully restored to the created file system.
SFS Metrics
General purpose file systems do not support monitoring. This section describes only the monitoring metrics of SFS Capacity-Oriented.
-Function
This section describes metrics reported by Scalable File Service (SFS) as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics generated for SFS.
+Function
This section describes the SFS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or APIs provided by Cloud Eye to query the SFS metrics and alarms.
+ Cloud Eye can monitor dimensions nested to a maximum depth of four levels (levels 0 to 3). 3 is the deepest level.
+Namespace
SYS.SFS
Metrics
-Table 1 SFS metrics Metric ID
+Table 1 SFS metrics Metric ID
Metric Name
+Metric Name
Description
+Description
Value Range
+Value Range
Monitored Object
+Unit
Monitoring Period (Raw Data)
+Conversion Rule
+Dimension
+Monitoring Period (Raw Data)
read_bandwidth
+read_bandwidth
Read Bandwidth
+Read Bandwidth
Read bandwidth of a file system within a monitoring period
-Unit: byte/s
+Read bandwidth of a file system within a monitoring period
≥ 0 bytes/s
+≥ 0
SFS file system
+bytes/s
4 minutes
+1024 (IEC)
+share_id
+4 minutes
write_bandwidth
+write_bandwidth
Write Bandwidth
+Write Bandwidth
Write bandwidth of a file system within a monitoring period
-Unit: byte/s
+Write bandwidth of a file system within a monitoring period
≥ 0 bytes/s
+≥ 0
SFS file system
+bytes/s
4 minutes
+1024 (IEC)
+share_id
+4 minutes
rw_bandwidth
+rw_bandwidth
Read and Write Bandwidth
+Read and Write Bandwidth
Read and write bandwidth of a file system within a monitoring period
-Unit: byte/s
+Read and write bandwidth of a file system within a monitoring period
≥ 0 bytes/s
+≥ 0
SFS file system
+bytes/s
4 minutes
+1024 (IEC)
+share_id
+4 minutes
read_ops
+read_ops
Read OPS
+Read OPS
Read operations of a file system within a monitoring period
-Unit: count/s
+Read operations of a file system within a monitoring period
≥ 0 counts/s
+≥ 0
SFS file system
+count/s
4 minutes
+N/A
+share_id
+4 minutes
write_ops
+write_ops
Write OPS
+Write OPS
Write operations of a file system within a monitoring period
-Unit: count/s
+Write operations of a file system within a monitoring period
≥ 0 counts/s
+≥ 0
SFS file system
+count/s
4 minutes
+N/A
+share_id
+4 minutes
rw_ops
+rw_ops
Read Write OPS
+Read Write OPS
Read and write operations of a file system within a monitoring period
-Unit: count/s
+Read and write operations of a file system within a monitoring period
≥ 0 counts/s
+≥ 0
SFS file system
+count/s
4 minutes
+N/A
+share_id
+4 minutes
used_capicity
+used_capicity
Used Capacity
+Used Capacity
Used capacity of a file system within a monitoring period
-Unit: byte
+Used capacity of a file system within a monitoring period
≥ 0 bytes
+≥ 0
SFS file system
+bytes
4 minutes
+1024 (IEC)
+share_id
+4 minutes
share_id
SFS file system
+SFS Capacity-Oriented
diff --git a/docs/sfs/umn/sfs_01_0048.html b/docs/sfs/umn/sfs_01_0048.html index e4e93e3d5..6eb2c2d01 100644 --- a/docs/sfs/umn/sfs_01_0048.html +++ b/docs/sfs/umn/sfs_01_0048.html @@ -1,136 +1,168 @@Viewing Monitoring Statistics
- Log in to the management console.
- Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Scalable File Service. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS file system monitoring data by metric or monitored duration.
Figure 1 shows the monitoring graphs. For more information about Cloud Eye, see the Cloud Eye User Guide.
- +
SFS Turbo Metrics
-Function
This section describes metrics reported by SFS Turbo to Cloud Eye as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics generated for SFS Turbo.
+Function
This section describes the SFS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or APIs provided by Cloud Eye to query the SFS metrics and alarms.
+ Cloud Eye can monitor dimensions nested to a maximum depth of four levels (levels 0 to 3). 3 is the deepest level.
+Namespace
SYS.EFS
Metrics
-Table 1 SFS Turbo metrics Metric ID
+-Table 1 SFS Turbo metrics Metric ID
Metric Name
+Metric Name
Description
+Description
Value Range
+Value Range
Monitored Object
+Unit
Monitoring Period (Raw Data)
+Conversion Rule
+Dimension
+Monitoring Period (Raw Data)
client_connections
+client_connections
File System Client Connections
+File System Client Connections
Number of client connections
+Number of client connections
NOTE:Only active client connections are counted.
A network connection is automatically disconnected when the client has no I/Os for a long time and is automatically re-established when there are I/Os.
≥ 0
+≥ 0
SFS Turbo file system
+count
1 minute
+N/A
+efs_instance_id
+1 minute
data_read_io_bytes
+data_read_io_bytes
Read Bandwidth
+Read Bandwidth
Data read I/O load
-Unit: byte/s
+Data read I/O load
≥ 0 bytes/s
+≥ 0
SFS Turbo file system
+bytes/s
1 minute
+1024 (IEC)
+efs_instance_id
+1 minute
data_write_io_bytes
+data_write_io_bytes
Write Bandwidth
+Write Bandwidth
Data write I/O load
-Unit: byte/s
+Data write I/O load
≥ 0 bytes/s
+≥ 0
SFS Turbo file system
+bytes/s
1 minute
+1024 (IEC)
+efs_instance_id
+1 minute
metadata_io_bytes
+metadata_io_bytes
Metadata Read and Write Bandwidth
+Metadata Read and Write Bandwidth
Metadata read and write I/O load
-Unit: byte/s
+Metadata read and write I/O load
≥ 0 bytes/s
+≥ 0
SFS Turbo file system
+bytes/s
1 minute
+1024 (IEC)
+efs_instance_id
+1 minute
total_io_bytes
+total_io_bytes
Total Bandwidth
+Total Bandwidth
Total I/O load
-Unit: byte/s
+Total I/O load
≥ 0 bytes/s
+≥ 0
SFS Turbo file system
+bytes/s
1 minute
+1024 (IEC)
+efs_instance_id
+1 minute
iops
+iops
IOPS
+IOPS
I/O operations per unit time
+I/O operations per unit time
≥ 0
+≥ 0
SFS Turbo file system
+count
1 minute
+N/A
+efs_instance_id
+1 minute
used_capacity
+used_capacity
Used Capacity
+Used Capacity
Used capacity of a file system
-Unit: byte
+Used capacity of a file system
≥ 0 bytes
+≥ 0
SFS Turbo file system
+byte
1 minute
+1024 (IEC)
+efs_instance_id
+1 minute
used_capacity_percent
+used_capacity_percent
Capacity Usage
+Capacity Usage
Percentage of used capacity in the total capacity
-Unit: percent
+Percentage of used capacity in the total capacity
0% to 100%
+0 - 100
SFS Turbo file system
+%
1 minute
+N/A
+efs_instance_id
+1 minute
diff --git a/docs/sfs/umn/sfs_01_0050.html b/docs/sfs/umn/sfs_01_0050.html index 03335b662..50a431ada 100644 --- a/docs/sfs/umn/sfs_01_0050.html +++ b/docs/sfs/umn/sfs_01_0050.html @@ -5,7 +5,6 @@Viewing Monitoring Statistics
- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Service List > Storage > Scalable File Service. In the file system list, click View Metric in the Operation column of the target file system.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > SFS Turbo. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS Turbo file system monitoring data by metric or monitored duration.
For more information about Cloud Eye, see the Cloud Eye User Guide.
+Viewing Monitoring Statistics
- Log in to the management console.
- View the monitoring graphs using either of the following methods.
- Method 1: Choose Service List > Storage > Scalable File Service. In the file system list, click View Metric in the Operation column of the target file system.
- Method 2: Choose Management & Deployment > Cloud Eye > Cloud Service Monitoring > Scalable File Service Turbo SFS Turbo. In the file system list, click View Metric in the Operation column of the desired file system.
- View the SFS Turbo file system monitoring data by metric or monitored duration.
For more information about Cloud Eye, see the Cloud Eye User Guide.
Only SFS Turbo file systems support recording of resource operations using CTS. SFS Capacity-Oriented and general purpose file systems do not support this function.
Prerequisites
You have enabled CTS and the tracker is normal. For details about how to enable CTS, see section "Enabling CTS" in the Cloud Trace Service User Guide.
--Operations
Table 1 SFS Capacity-Oriented operations traced by CTS Operation
@@ -95,12 +94,12 @@diff --git a/docs/sfs/umn/sfs_01_0052.html b/docs/sfs/umn/sfs_01_0052.html index fa5e96334..084d65cea 100644 --- a/docs/sfs/umn/sfs_01_0052.html +++ b/docs/sfs/umn/sfs_01_0052.html @@ -7,12 +7,12 @@Querying Traces
- Log in to the management console.
- Click
in the upper left corner and select a region and project. - Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
+Querying Traces
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
- In the navigation pane on the left, choose Trace List.
- On the trace list page, set Trace Source, Resource Type, and Search By, and click Query to query the specified traces.
For details about other operations, see section "Querying Real-Time Traces" in the Cloud Trace Service User Guide.
Disabling or Enabling a Tracker
This section describes how to disable an existing tracker on the CTS console. After the tracker is disabled, the system will stop recording operations, but you can still view existing operation records.
-- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
+- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Choose Management & Deployment > Cloud Trace Service.
The Cloud Trace Service page is displayed.
- Click Trackers in the left pane.
- Click Disable on the right of the tracker information.
- Click Yes.
- After the tracker is disabled, the available operation changes from Disable to Enable. To enable the tracker again, click Enable and then click Yes. The system will start recording operations again.
- Energy exploration: Field operations, geologic prospecting, geological data processing and interpretation, and identification of oil and gas reservoirs all require large memory and high bandwidth of the file system.
- Image rendering: Image processing, 3D rendering, and frequent processing of small files require high read/write performance, large capacity, and high bandwidth of file systems.
- Heterogeneous computing: Compute elements may have different instruction set architectures, requiring the file system provide high bandwidth and low latency.
SFS is a shared storage service based on file systems. It features high-speed data sharing, dynamic storage tiering, as well as on-demand, smooth, and online resizing. These outstanding features empower SFS to meet the demanding requirements of HPC on storage capacity, throughput, IOPS, and latency.
A biological company needs to perform plenty of gene sequencing using software. However, due to the trivial steps, slow deployment, complex process, and low efficiency, self-built clusters are reluctant to keep abreast of business development. However, things are getting better since the company resorted to professional HPC service process management software. With massive compute and storage resource of the cloud platform, the initial investment and cost during O&M are greatly reduced, the service rollout time is shortened, and efficiency is boosted.
-Configuration Process
- Organize the files of DNA sequencing to be uploaded.
- Log in to the SFS console. Create a file system to store the files of DNA sequencing.
- Log in to the servers that function as the head node and compute node, and mount the file system.
- On the head node, upload the files to the file system.
- On the compute node, edit the files.
-Configuration Process
- Organize the files of DNA sequencing to be uploaded.
- Log in to the SFS console. Create a file system to store the files of DNA sequencing.
- Log in to the cloud servers that function as the head node and compute node, and mount the file system on them, respectively.
- On the head node, upload the files to the file system.
- On the compute node, edit the files.
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.
-Prerequisites
- A VPC has been created.
- Cloud servers that function as the head node and compute node have been created and are in the created VPC.
- SFS has been enabled.
Example Configuration
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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).
- - Log in to the head node, and upload the files to the file system.
- Start gene sequencing, and the compute node obtains the gene sequencing file from the mounted file system for calculation.
Example Configuration
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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).
+ - Log in to the head node and upload the files to the file system.
- 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 93a2c7e50..6ca66006a 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.
diff --git a/docs/sfs/umn/sfs_01_0054.html b/docs/sfs/umn/sfs_01_0054.html index 9f222e7d6..437412e8c 100644 --- a/docs/sfs/umn/sfs_01_0054.html +++ b/docs/sfs/umn/sfs_01_0054.html @@ -1,14 +1,14 @@Example Configuration
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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).
- Log in to the upload workstations, and upload the material files to the file system.
- Log in to the editing workstations, and edit the material files.
Enterprise Website/App Background
-Context
For I/O-intensive website services, SFS Turbo can provide shared website source code directories and storage for multiple web servers, enabling low-latency and high-IOPS concurrent share access. Features of such services are as follows:
+-Context
For I/O-intensive website services, SFS Turbo can provide shared website source code directories and storage for multiple web servers, enabling low-latency and high-IOPS concurrent shared access. Features of such services are as follows:
- A large number of small files: Static website files need to be stored, including HTML files, JSON files, and static images.
- Read I/O intensive: Scope of data reading is large, and data writing is relatively small.
- Multiple web servers access an SFS Turbo background to achieve high availability of website services.
Configuration Process
- Sort out the website files.
- Log in to the SFS console. Create an SFS Turbo file system to store the website files.
- Log in to the server that functions as the compute node and mount the file system.
- On the head node, upload the files to the file system.
- Start the web server.
-Configuration Process
- Sort out the website files.
- Log in to the SFS console. Create an SFS Turbo file system to store the website files.
- Log in to the cloud server that functions as the compute node and mount the file system.
- On the head node, upload the files to the file system.
- Start the web server.
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.
-Prerequisites
- A VPC has been created.
- Cloud servers that function as the head node and compute node have been created and are in the created VPC.
- SFS has been enabled.
diff --git a/docs/sfs/umn/sfs_01_0055.html b/docs/sfs/umn/sfs_01_0055.html index de0e8944a..5eb4e4796 100644 --- a/docs/sfs/umn/sfs_01_0055.html +++ b/docs/sfs/umn/sfs_01_0055.html @@ -1,14 +1,14 @@Example Configuration
- Log in to the SFS console.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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
- Log in to the SFS console.
- In the navigation pane on the left, choose SFS Turbo > File Systems. In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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).
- Log in to the head node and upload the files to the file system.
- Start the web server.
Log Printing
-Context
SFS Turbo can provide multiple service nodes for shared log output directories, facilitating log collection and management of distributed applications. Features of such services are as follows:- A shared file system is mounted to multiple service hosts and logs are printed concurrently.
- Large file size and small I/O: The size of a single log file is large, but the I/O of each log writing is small.
- Write I/O intensive: Write I/O of small blocks is the major service.
-Context
SFS Turbo can provide shared log output directories for multiple service nodes, facilitating log collection and management of distributed applications. Features of such services are as follows:- A shared file system is mounted to multiple service hosts and logs are printed concurrently.
- Large file size and small I/O: The size of a single log file is large, but the I/O of each log writing is small.
- Write I/O intensive: Write I/O of small blocks is the major service.
Configuration Process
- Log in to the SFS console. Create an SFS Turbo file system to store the log files.
- Log in to the server that functions as the compute node and mount the file system.
- Configure the log directory to the shared file system. It is recommended that each host use different log files.
- Start applications.
-Configuration Process
- Log in to the SFS console. Create an SFS Turbo file system to store the log files.
- Log in to the cloud server that functions as the compute node and mount the file system.
- Configure the log directory to the shared file system. It is recommended that each host use different log files.
- Start applications.
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.
-Prerequisites
- A VPC has been created.
- Cloud servers that function as the head node and compute node have been created and are in the created VPC.
- SFS has been enabled.
diff --git a/docs/sfs/umn/sfs_01_0056.html b/docs/sfs/umn/sfs_01_0056.html index fafce3d30..99fdc0d1d 100644 --- a/docs/sfs/umn/sfs_01_0056.html +++ b/docs/sfs/umn/sfs_01_0056.html @@ -12,9 +12,9 @@Example Configuration
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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
- Log in to the SFS console.
- In the upper right corner of the page, click Create File System.
- On the Create File System page, set parameters as instructed.
- 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).
- Configure the log directory to the shared file system. It is recommended that each host use different log files.
- Start applications.
- A File System Is Automatically Disconnected from the Server
-
- A Server Fails to Access a File System
+- A Client Server Failed to Access a File System
-
- The File System Is Abnormal
+- File System Is Abnormal
- Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
diff --git a/docs/sfs/umn/sfs_01_0057.html b/docs/sfs/umn/sfs_01_0057.html index 913ef50ff..485eb400f 100644 --- a/docs/sfs/umn/sfs_01_0057.html +++ b/docs/sfs/umn/sfs_01_0057.html @@ -1,19 +1,19 @@
Mounting a File System Fails
-Symptom
When a file system is mounted to servers using the mount command, message access denied is displayed.
+-Symptom
When a file system was mounted to a cloud server using the mount command, message "access denied" was displayed on the server.
Possible Causes
- Cause 1: The file system has been deleted.
- Cause 2: The server and the mounted file system are not in the same VPC.
- Cause 3: The mount point in the mount command is incorrect.
- Cause 4: The IP address used for accessing SFS is a virtual IP address.
- Cause 5: The DNS used for accessing the file system is incorrect.
Possible Causes
- Cause 1: The file system has been deleted.
- Cause 2: The server and the file system are not in the same VPC.
- Cause 3: The mount point in the mount command is incorrect.
- Cause 4: The IP address used for accessing SFS is a virtual IP address.
- Cause 5: The DNS used for accessing the file system is incorrect.
-Fault Diagnosis
Take troubleshooting measures based on possible causes.
Solution
- Cause 1: The file system has been deleted.Log in to the management console and check whether the file system has been deleted.
- If yes, create a file system or select an existing file system to mount. Ensure that the server and the file system reside in the same VPC.
- If no, go to Cause 2.
Solution
- Cause 1: The file system has been deleted. -
- Cause 2: The server and the mounted file system are not in the same VPC.Log in to the management console and check whether the server and the file system belong to the same VPC.
- If yes, go to Cause 3.
- If no, select a file system that resides in the same VPC as the server.
- Cause 2: The server and the file system are not in the same VPC. -
- Cause 3: The mount point in the mount command is incorrect.
- Log in to the management console and check whether the mount point is the same as the one in the mount command.
- If the mount point in the mount command is incorrectly entered, correct it and run the command again.
- Cause 3: The mount point in the mount command is incorrect.
- Log in to the management console and check whether the mount point is the same as the one in the mount command.
- If the mount point in the mount command is incorrectly entered, correct it and run the command again.
- Cause 4: The IP address used for accessing SFS is a virtual IP address.
Log in to the server and run the ping command and use the server IP address to access SFS. Check whether the service is reachable. See Figure 1.
-- If yes, the network problem has been resolved. Check other possible causes.
- If no, the server virtual IP address is unable to access SFS due to the network problem. Use the private IP address and run the ping command to access SFS and check whether the service is reachable.
+
- If yes, the network problem has been resolved. Check other possible causes.
- If no, the network is disconnected. Use the server's private IP address and the ping command to access SFS and check whether the service is reachable.
- Cause 5: The DNS used for accessing the file system is incorrect.
Run the following command to check whether the DNS is correct:
nslookup File system domain name
diff --git a/docs/sfs/umn/sfs_01_0058.html b/docs/sfs/umn/sfs_01_0058.html index 6b77d45cd..17cfa960c 100644 --- a/docs/sfs/umn/sfs_01_0058.html +++ b/docs/sfs/umn/sfs_01_0058.html @@ -1,15 +1,15 @@ -A Server Fails to Access a File System
-Symptom
A server fails to access a file system. The system displays a message indicating that the access request is denied. All services on the server are abnormal.
+A Client Server Failed to Access a File System
+-Symptom
Access from a client server to a file system was denied. All services on the server were abnormal.
Possible Causes
- Cause 1: The file system is abnormal.
- Cause 2: After a forcible unmount operation on the server, mount fails.
Possible Causes
- Cause 1: The file system is abnormal.
- Cause 2: The file system fails to be mounted to the server after being forcibly unmounted.
Fault Diagnosis
Take troubleshooting measures based on possible causes.
diff --git a/docs/sfs/umn/sfs_01_0059.html b/docs/sfs/umn/sfs_01_0059.html index 813500e6b..616ee9e6f 100644 --- a/docs/sfs/umn/sfs_01_0059.html +++ b/docs/sfs/umn/sfs_01_0059.html @@ -1,7 +1,7 @@ -Solution
- Cause 1: The file system is abnormal.
Log in to the management console. On the Scalable File System page, check whether the file system is in the Available state.
-- If yes, go to Cause 2.
- If no, see The File System Is Abnormal to restore the file system to the available state, and then access the file system again.
- Cause 2: After a forcible unmount operation on the server, mount fails.
- This problem is caused by an inherent defect of servers. Restart the server to resolve this problem.
- Check whether the file system can be properly mounted and accessed.
- If yes, no further action is required.
- If no, contact technical support.
- If yes, go to Cause 2.
- If no, see File System Is Abnormal to restore the file system to the available state, and then access the file system again.
- Cause 2: The file system fails to be mounted to the server after being forcibly unmounted.
- This problem is caused by a defect of servers. Restart the server to resolve this problem.
- Check whether the file system can be properly mounted and accessed from the server.
- If yes, no further action is required.
- If no, contact technical support.
The File System Is Abnormal
-Currently, the file system exceptions include deletion error, expansion error, reduction error, and reduction failure. When the file system is in these statuses, refer to the following handling suggestions.
+File System Is Abnormal
+Currently, the file system exceptions include reduction error, reduction failure, deletion error and expansion error. When the file system is in these statuses, refer to the following handling suggestions.
Table 1 Measures for handling file system abnormalities Exception
-Fault Diagnosis
To address this problem, modify the registry and change both UID and GID values to 0 for NFS accesses from Windows.
diff --git a/docs/sfs/umn/sfs_01_0061.html b/docs/sfs/umn/sfs_01_0061.html index a7866bc3d..daa264c84 100644 --- a/docs/sfs/umn/sfs_01_0061.html +++ b/docs/sfs/umn/sfs_01_0061.html @@ -7,8 +7,8 @@Solution
- Choose Start > Run and enter regedit to open the registry.
- Enter the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default directory. Figure 1 shows an example of the directory. -
- Right-click the blank area and choose New > DWORD Value from the shortcut menu. Set AnonymousUid and AnonymousGid to 0. Figure 2 shows a successful operation.
+
Solution
- Choose Start > Run and enter regedit to open the registry.
- Enter the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default directory. Figure 1 shows an example of the directory. +
- Right-click the blank area and choose New > DWORD Value from the shortcut menu. Set AnonymousUid and AnonymousGid to 0. Figure 2 shows a successful operation.
- After modifying the registry, restart the server for the modification to take effect.
-Fault Diagnosis
Take troubleshooting measures based on possible causes.
Solution
- Log in to the ECS. An ECS running Windows Server 2012 R2 is used in this example.
- Click Server Manager in the lower left corner.
- Choose Tools > Internet Information Services (IIS) Manager, expand Sites, and select the target website.
- Click Basic Settings to check whether the Physical path is correct.
- The correct physical path is that of the mount point with the colon (:) deleted.Figure 1 shows the mount point of a file system. You need to enter the physical path \\sfs-nas1.example.com\share-396876e8, as shown in Figure 2. - +diff --git a/docs/sfs/umn/sfs_01_0062.html b/docs/sfs/umn/sfs_01_0062.html index b80af2fa4..a5a7f4c6b 100644 --- a/docs/sfs/umn/sfs_01_0062.html +++ b/docs/sfs/umn/sfs_01_0062.html @@ -8,13 +8,13 @@
Solution
- Log in to the cloud server. An ECS running Windows Server 2012 R2 is used in this example.
- Click Server Manager in the lower left corner.
- Choose Tools > Internet Information Services (IIS) Manager, expand Sites, and select the target website.
- Click Basic Settings to check whether the Physical path is correct.
- The correct physical path is that of the mount point with the colon (:) deleted.
Fault Diagnosis
Install the required nfs-utils software package.
Solution
- Log in to the ECS and check whether the nfs-utils package is installed. Run the following command. If no command output is displayed, the package is not installed.
rpm -qa|grep nfs
-Figure 1 Checking whether the software package has been installed+
Figure 1 Checking whether the software package has been installed - Run the following command to install the nfs-utils software package:
yum -y install nfs-utils
-Figure 2 Executing the installation command-
Figure 3 Successful installation+
Figure 2 Executing the installation command+Figure 3 Successful installation - Run the mount command again to mount the file system to the ECS.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path
- Run the following command to view the mounted file system:
mount -l
-If the command output contains the following information, the file system is mounted successfully.diff --git a/docs/sfs/umn/sfs_01_0063.html b/docs/sfs/umn/sfs_01_0063.html index fb3597452..68e61e990 100644 --- a/docs/sfs/umn/sfs_01_0063.html +++ b/docs/sfs/umn/sfs_01_0063.html @@ -1,7 +1,7 @@example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
+If the command output contains the following information, the file system has been mounted:example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
Failed to Access the Shared Folder in Windows
-diff --git a/docs/sfs/umn/sfs_01_0067.html b/docs/sfs/umn/sfs_01_0067.html index eaeb498a3..5f03c0262 100644 --- a/docs/sfs/umn/sfs_01_0067.html +++ b/docs/sfs/umn/sfs_01_0067.html @@ -3,7 +3,7 @@Symptom
When you mount a file system to an ECS running Windows, the system displays a message "You cannot access this shared folder because your organization's security policies block unauthenticated guest access. These policies help to protect you PC from unsafe or malicious devices on the network."
+Symptom
When you mount a file system to an ECS running Windows, the system displays a message "You cannot access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network."
@@ -9,14 +9,14 @@Possible Causes
Guest access to CIFS file systems is blocked or disabled.
Solution 2: Modify the registry to allow guest access (suitable for versions later than Windows Server 2016).
Solution
Solution 1: Manually enable guest access.
-- Open Run command box, enter gpedit.msc, and press Enter to start Local Group Policy Editor.Figure 1 Entering gpedit.msc-
- On the Local Group Policy Editor page, choose Computer Configuration > Administrative Templates.Figure 2 Local Group Policy Editor-
- Under Administrative Templates, choose Network > Lanman Workstation and find the option of Enable insecure guest logons.Figure 3 Locating the option-
- Double-click Enable insecure guest logons. Select Enabled and click OK.Figure 4 Enabling insecure guest logons+
- Open the Run command box, enter gpedit.msc, and press Enter to start Local Group Policy Editor.Figure 1 Entering gpedit.msc+
- On the Local Group Policy Editor page, choose Computer Configuration > Administrative Templates.Figure 2 Local Group Policy Editor+
- Under Administrative Templates, choose Network > Lanman Workstation and find the option Enable insecure guest logons.Figure 3 Locating the option+
- Double-click Enable insecure guest logons. Select Enabled and click OK.Figure 4 Enabling insecure guest logons
- After the access is enabled, mount the file system again. If the fault persists, contact technical support.
Solution 2: Modify the registry to allow guest access (suitable for versions later than Windows Server 2016).
-- Choose Start > Run and enter regedit to open the registry.
- Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters directory.Figure 5 Entering the registry-
- Right-click AllowInsecureGuestAuth and choose Modify from the shortcut menu. In the pop-up window, change the value to 1.Figure 6 Changing the value+
- Choose Start > Run and enter regedit to open the registry.
- Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters directory.Figure 5 Entering the registry+
- Right-click AllowInsecureGuestAuth and choose Modify from the shortcut menu. In the pop-up window, change the value to 1.Figure 6 Changing the value
- Open the Run command box, enter gpedit.msc, and press Enter to start Local Group Policy Editor.
What Is SFS?
Scalable File Service (SFS) provides scalable, high-performance file storage. With SFS, you can enjoy shared file access spanning multiple ECSs. SFS supports the Network File System (NFS) protocol. You can seamlessly integrate existing applications and tools with the service.
SFS provides an easy-to-use graphical user interface (GUI). On the GUI, users can create and configure file systems, saving effort in deploying, resizing, and optimizing file systems.
-In addition, SFS features high availability. It can be elastically expanded, and it performs better as its capacity grows. The service is suitable for a wide range of scenarios, including media processing, file sharing, content management and web services, big data, and analytic applications.
+In addition, SFS features high availability. It can be elastically expanded, and it performs better as its capacity grows. It is suitable for a wide range of scenarios, including media processing, file sharing, content management and web services, big data, and analytic applications.
diff --git a/docs/sfs/umn/sfs_01_0068.html b/docs/sfs/umn/sfs_01_0068.html index 2c14e3ebd..085110e48 100644 --- a/docs/sfs/umn/sfs_01_0068.html +++ b/docs/sfs/umn/sfs_01_0068.html @@ -3,7 +3,7 @@What Is SFS Turbo?
SFS Turbo provides high-performance file storage that can be expanded on demand. With SFS Turbo, you can enjoy shared file access spanning multiple ECSs. SFS Turbo supports the Network File System (NFS) protocol (only NFSv3). You can seamlessly integrate existing applications and tools with the service.
SFS Turbo provides an easy-to-use graphical user interface (GUI). On the GUI, users can create and configure file systems, saving effort in deploying, resizing, and optimizing file systems.
-In addition, SFS Turbo features high reliability and availability. It can be elastically expanded, and it performs better as its capacity grows. The service is suitable for a wide range of scenarios, including enterprise office, high-performance websites, and software development. For details about SFS Turbo file system types, see File System Types.
+In addition, SFS Turbo features high reliability and availability. It can be elastically expanded, and it performs better as its capacity grows. The service is suitable for a wide range of scenarios, including enterprise office, high-performance websites, and software development. For details about the file system types, see File System Types.
diff --git a/docs/sfs/umn/sfs_01_0070.html b/docs/sfs/umn/sfs_01_0070.html index 2633e5411..4970dc347 100644 --- a/docs/sfs/umn/sfs_01_0070.html +++ b/docs/sfs/umn/sfs_01_0070.html @@ -14,7 +14,7 @@- How Many File Systems Can Be Created by Each Account?
-
- How Many Servers Can a File System Be Mounted To?
+- How Many Cloud Servers Can I Mount a File System To?
diff --git a/docs/sfs/umn/sfs_01_0073.html b/docs/sfs/umn/sfs_01_0073.html index 08059c56f..16b2df491 100644 --- a/docs/sfs/umn/sfs_01_0073.html +++ b/docs/sfs/umn/sfs_01_0073.html @@ -1,8 +1,8 @@
How Many File Systems Can Be Created by Each Account?
-Each account can create a maximum of 10 SFS Capacity-Oriented file systems and 10 SFS Turbo file systems.
-Each account can create a maximum of 100 general purpose file systems.
+You can create a maximum of 10 SFS Capacity-Oriented file systems and 10 SFS Turbo file systems with each account.
+You can create a maximum of 100 general purpose file systems with one account.
- SFS Capacity-Oriented file systems can be created in batches. To create more than 10 SFS Capacity-Oriented file systems, click Increase quota on the page for creating a file system.
- Only one SFS Turbo file system can be created at a time. To create more than 10 SFS Turbo file systems, contact customer service to apply for a higher quota. For details, see How Do I Apply for a Higher Quota?
diff --git a/docs/sfs/umn/sfs_01_0074.html b/docs/sfs/umn/sfs_01_0074.html index d52d381bc..f64c25842 100644 --- a/docs/sfs/umn/sfs_01_0074.html +++ b/docs/sfs/umn/sfs_01_0074.html @@ -1,6 +1,6 @@ -How Many Servers Can a File System Be Mounted To?
+How Many Cloud Servers Can I Mount a File System To?
You can mount an SFS Capacity-Oriented file system to a maximum of 10,000 servers.
You can mount an SFS Turbo file system to a maximum of 3,000 servers.
You can mount a general purpose file system to a maximum of 10,000 servers.
diff --git a/docs/sfs/umn/sfs_01_0080.html b/docs/sfs/umn/sfs_01_0080.html index 99a543533..f405c0cf3 100644 --- a/docs/sfs/umn/sfs_01_0080.html +++ b/docs/sfs/umn/sfs_01_0080.html @@ -2,7 +2,7 @@Can a File System Be Accessed Across VPCs?
Yes.
-- Multi-VPC access can be configured for an SFS Capacity-Oriented or a general purpose file system so that ECSs in different VPCs can share the same file system, as long as the VPCs that the ECSs belong to are added to the VPC list of the file system or the ECS IP addresses are added as authorized IP addresses of the VPCs. For details, see Configuring Multi-VPC Access.
- An SFS Turbo file system allows two or more VPCs in the same region to interconnect with each other through VPC peering connection. In this case, different VPCs are in the same network, and ECSs in these VPCs can share the same file system. For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
- Multi-VPC access can be configured for an SFS Capacity-Oriented or a general purpose file system so that servers in different VPCs can share the same file system, as long as the VPCs that the servers belong to are added as authorized VPCs of the file system or the server IP addresses are added as authorized IP addresses of the VPCs. For details, see Configuring Multi-VPC Access.
- An SFS Turbo file system allows two or more VPCs in the same region to interconnect with each other through VPC peering connection. In this case, different VPCs are in the same network, and servers in these VPCs can share the same file system. For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
diff --git a/docs/sfs/umn/sfs_01_0081.html b/docs/sfs/umn/sfs_01_0081.html index 648764922..f6c43e939 100644 --- a/docs/sfs/umn/sfs_01_0081.html +++ b/docs/sfs/umn/sfs_01_0081.html @@ -1,7 +1,7 @@Does the Security Group of a VPC Affect SFS?
-A security group is a collection of access control rules for servers that have the same security protection requirements and are mutually trusted in a VPC. After a security group is created, you can create different access rules for the security group to protect the servers that are added to this security group. The default security group rule allows all outgoing data packets. Servers in a security group can access each other without the need to add rules. The system creates a security group for each cloud account by default. Users can also create custom security groups by themselves.
+-A security group is a collection of access control rules for ECSs that have the same security protection requirements and are mutually trusted in a VPC. After a security group is created, you can create different access rules for the security group to protect ECSs that are added to this security group. The default security group rule allows all outgoing data packets. ECSs in a security group can access each other without the need to add rules. The system creates a security group for each cloud account by default. Users can also create custom security groups by themselves.
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.
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 section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. In 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.
@@ -66,7 +66,7 @@diff --git a/docs/sfs/umn/sfs_01_0082.html b/docs/sfs/umn/sfs_01_0082.html index 707bbba41..d6f3515c3 100644 --- a/docs/sfs/umn/sfs_01_0082.html +++ b/docs/sfs/umn/sfs_01_0082.html @@ -7,7 +7,7 @@ Enter an IP address range using a mask. For example, enter 192.168.1.0/24, and do not enter 192.168.1.0-192.168.1.255. If the source IP address is 0.0.0.0/0, all IP addresses are allowed.
The bidirectional access rule must be configured for port 111. The inbound rule can be set to the front-end service IP range of SFS. You can obtain it by running the following command: ping File system domain name or IP address or dig File system domain name or IP address.
For ports 2049, 2050, 2051, and 2052, only the outbound rule needs to be added, which is the same as the outbound rule of port 111.
-For the NFS protocol, add an inbound rule to open the TCP&UDP port 111, TCP ports 2049, 2051, and 2052, and UDP&TCP port 20048.
+For the NFS protocol, add an inbound rule to open the TCP and UDP port 111, TCP ports 2049, 2051, and 2052, and UDP and TCP port 20048.
For the NFS protocol with UDP port 20048 not opened, the time required for mounting may become longer. In this case, you can use the -o tcp option in mount to avoid this issue.
The noac option disables file attribute caching and forces write synchronization. By default, an NFS client's file attribute information is cached using the ac option to improve performance, and the client checks file attribute information periodically and updates it if there are any changes. Within the cache validity period, the client does not check whether file attribute information on the server is changed. By default, the value of this option is ac. Set it to noac.
The lookupcache option is related to directory entry caching, and the value can be all, none, pos, or positive. With lookupcache=none, the client neither trust the positive nor negative lookup results. In this way, lookup caching is disabled.
diff --git a/docs/sfs/umn/sfs_01_0091.html b/docs/sfs/umn/sfs_01_0091.html index 3fec0dde0..2e50a69ec 100644 --- a/docs/sfs/umn/sfs_01_0091.html +++ b/docs/sfs/umn/sfs_01_0091.html @@ -4,7 +4,7 @@Solution
- Unmount the file system if it has been mounted. To unmount a file system, see Unmount a File System.
- Complete the preparations before mounting the file system. For details, see Mounting an NFS File System to ECSs (Linux).
- Mount the file system.
mount -t nfs -o vers=3,timeo=600,noac,lookupcache=none,noresvport,nolock Shared path Local path
+Solution
- Unmount the file system if it has been mounted. For details, see Unmount a File System.
- Prepare for the mount by referring to Mounting an NFS File System to ECSs (Linux).
- Mount the file system.
mount -t nfs -o vers=3,timeo=600,noac,lookupcache=none,noresvport,nolock Shared path Local path
-
-
- How Do I Access a File System from a Server?
+ - How Do I Access a File System from a Client Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
diff --git a/docs/sfs/umn/sfs_01_0092.html b/docs/sfs/umn/sfs_01_0092.html
index ecf31ddff..3924e922e 100644
--- a/docs/sfs/umn/sfs_01_0092.html
+++ b/docs/sfs/umn/sfs_01_0092.html
@@ -1,7 +1,7 @@
- - For SFS Capacity-Oriented or general purpose file systems:
- When a file system is created, the inbound rules of ports 111, 445, 2049, 2051, and 2052 are enabled in the security group entered by the user. The default source IP address is 0.0.0.0/0. You can change the IP address as required.
- If an encrypted SFS Capacity-Oriented file system is created, the KMS key entered by the user is used for encryption. Note that if the key is deleted, data in the file system cannot be used.
- For SFS Turbo file systems:
- When an SFS Turbo file system is created, two private IP addresses and one virtual IP address are created in the subnet entered by the user.
- When an SFS Turbo file system is created, the inbound rules of ports 111, 445, 2049, 2051, 2052, and 20048 are enabled in the security group entered by the user. The default source IP address is 0.0.0.0/0. You can change the IP address as required.
- If an encrypted SFS Turbo file system is created, the KMS key entered by the user is used for encryption. Note that if the key is deleted, data in the file system cannot be used.
- For SFS Turbo file systems:
- When an SFS Turbo file system is created, two private IP addresses and one virtual IP address are created in the subnet entered by the user.
- When an SFS Turbo file system is created, the inbound rules of ports 111, 445, 2049, 2051, 2052, and 20048 are enabled in the security group selected by the user. The default source IP address is 0.0.0.0/0. You can change the IP address as required.
- If an encrypted SFS Turbo file system is created, the KMS key entered by the user is used for encryption. Note that if the key is deleted, data in the file system cannot be used.
- A non-root user has been created on the ECS.
- A file system has been created and can be mounted to the ECS as root.
- The mount point of the file system has been obtained.
- Log in to the ECS as user root.
- Assign the permissions of user root to the non-root user.
- Run the chmod 777 /etc/sudoers command to change the sudoers file to be editable.
- Use the which command to view the mount and umount command paths.Figure 1 Viewing command paths-
- Run the vi /etc/sudoers command to edit the sudoers file.
- Add a common user under the root account. In this example, user Mike is added.Figure 2 Adding a user+
Procedure
- Log in to the ECS as user root.
- Assign the permissions of user root to the non-root user.
- Run the chmod 777 /etc/sudoers command to change the sudoers file to be editable.
- Use the which command to view the mount and umount command paths.Figure 1 Viewing command paths+
- Run the vi /etc/sudoers command to edit the sudoers file.
- Add a common user under the root account. In this example, user Mike is added.Figure 2 Adding a user
- Press Esc, input :wq, and press Enter to save and exit.
- Run the chmod 440 /etc/sudoers command to change the sudoers file to be read-only.
- Log in to the ECS as user Mike.
- Run the following command to mount the file system. For details about the mounting parameters, see Table 1.
sudo mount -t nfs -o vers=3,timeo=600,noresvport,nolock Mount point Local path
@@ -33,7 +33,7 @@
How Do I Access a File System from a Server?
-To access your file system, install the NFS client on a Linux server and run the mount command to mount the file system. For a Windows server, install the NFS client, modify the NFS transfer protocol, and run the mount command to mount the file system. Then, you can share the files and directories of the file system.
+How Do I Access a File System from a Client Server?
+To access a file system from a Linux server, install the NFS client on the server and run mount to mount the file system. To access a file system from a Windows server, install the NFS client on the server, modify the NFS transfer protocol, and run command to mount the file system. Then, you can share the files and directories in the file system.
diff --git a/docs/sfs/umn/sfs_01_0094.html b/docs/sfs/umn/sfs_01_0094.html index 6ec3d1004..5ade59c13 100644 --- a/docs/sfs/umn/sfs_01_0094.html +++ b/docs/sfs/umn/sfs_01_0094.html @@ -3,7 +3,7 @@What Resources Does SFS Occupy?
diff --git a/docs/sfs/umn/sfs_01_0100.html b/docs/sfs/umn/sfs_01_0100.html index f61693227..eadab0e79 100644 --- a/docs/sfs/umn/sfs_01_0100.html +++ b/docs/sfs/umn/sfs_01_0100.html @@ -1,12 +1,12 @@To ensure that file systems can be used properly, the service occupies the following resources:
When data is written to the folders of a file system, the running memory of the server is occupied, but the storage space of the server disk is not occupied. The file system uses independent space.
Mounting a File System to a Linux ECS as a Non-root User
-Scenarios
By default, a Linux ECS allows only the root user to use the mount command to mount file systems, but you can grant the permissions of user root to other users. Then, such users can use the mount command to mount the file systems. The following describes how to mount a file system to a Linux ECS as a common user. EulerOS is used in this example.
+Scenarios
By default, a Linux ECS allows only the root user to use the mount command to mount file systems, but you can grant the permissions of user root to other users. Such users can then use the mount command to mount the file systems. The following describes how to mount a file system to a Linux ECS as a non-root user. EulerOS is used in this example.
-Prerequisites
Procedure
- Open Run command box, enter gpedit.msc, and press Enter to start Local Group Policy Editor.
- 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.diff --git a/docs/sfs/umn/sfs_01_0101.html b/docs/sfs/umn/sfs_01_0101.html index e145019f1..c2cbdab5a 100644 --- a/docs/sfs/umn/sfs_01_0101.html +++ b/docs/sfs/umn/sfs_01_0101.html @@ -4,7 +4,11 @@example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
+If the command output contains the following information, the file system has been mounted:example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
diff --git a/docs/sfs/umn/sfs_01_0104.html b/docs/sfs/umn/sfs_01_0104.html index 162ec3a7c..68767e5ea 100644 --- a/docs/sfs/umn/sfs_01_0104.html +++ b/docs/sfs/umn/sfs_01_0104.html @@ -8,7 +8,19 @@
2024-12-20
+2025-10-16
+Updated the following content:
+- Updated section Create a File System.
- Updated section Mounting an NFS File System to ECSs (Linux).
- Added section Migrating Data from SFS Capacity-Oriented to Other File Systems Using rclone.
- Added section Migrating Data from SFS Capacity-Oriented to General-Purpose File System Using fpart.
- Added section Migrating Data from SFS Capacity-Oriented to SFS Turbo Using fpart.
- Deleted section "Migrating Data Between File Systems."
- Deleted section "Supported Operating Systems."
- Added tag-related content for general purpose file systems.
- Updated tag-related content for SFS Turbo file systems.
2025-09-28
+Updated the following content:
+Modified the description in section Mounting an NFS File System to ECSs (Linux).
+2024-12-20
Updated the following content:
Added section Managing SFS Turbo+OBS Storage Interworking.
diff --git a/docs/sfs/umn/sfs_01_0117.html b/docs/sfs/umn/sfs_01_0117.html deleted file mode 100644 index 32a049ceb..000000000 --- a/docs/sfs/umn/sfs_01_0117.html +++ /dev/null @@ -1,30 +0,0 @@ - - -Migrating Data Between File Systems
---Solution Overview
You can migrate data from an SFS Capacity-Oriented file system to an SFS Turbo file system or the other way around.
-This solution creates a Linux ECS to connect an SFS Capacity-Oriented file system with an SFS Turbo file system.
--Limitations and Constraints
- Only Linux ECSs can be used to migrate data.
- The Linux ECS, SFS Capacity-Oriented file system, and SFS Turbo file system must be in the same VPC.
- Incremental migration is supported, so that only changed data is migrated.
-Prerequisites
- You have created a Linux ECS.
- You have created an SFS Capacity-Oriented file system and an SFS Turbo file system and have obtained their mount points.
-Procedure
- Log in to the ECS console.
- Log in to the created Linux ECS that can access SFS Capacity-Oriented and SFS Turbo file systems.
- Run the following command to mount file system 1 (either the SFS Capacity-Oriented or SFS Turbo file system). After that, you can access file system 1 on the Linux ECS.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock [Mount point of file system 1] /mnt/src
- - Run the following command to mount file system 2 (the other file system that you have not mounted in the previous step). After that, you can access file system 2 on the Linux ECS.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock [Mount point of file system 2] /mnt/dst
- - Download and install rclone. For the download address, see https://rclone.org/downloads/.
- Run the following command to synchronize data:
rclone copy /mnt/src /mnt/dst -P --transfers 32 --checkers 64 --links --create-empty-src-dirs
-- Set transfers and checkers based on the system specifications. The parameters are described as follows:
-- /mnt/src: source path
- /mnt/dst: destination path
- --transfers: number of files that can be transferred concurrently
- --checkers: number of local files that can be scanned concurrently
- -P: data copy progress
- --links: replicates the soft links from the source. They are saved as soft links in the destination.
- --copy-links: replicates the content of files to which the soft links point. They are saved as files rather than soft links in the destination.
- --create-empty-src-dirs: replicates the empty directories from the source to the destination.
After data synchronization is complete, go to the target file system to check whether data is migrated.
-
-Verification
- Log in to the created Linux ECS.
- Run the following commands on the destination server to verify file synchronization:
cd /mnt/dst -ls | wc -l
- - If the data volume is the same as that on the source server, the data is migrated successfully.
-- diff --git a/docs/sfs/umn/sfs_01_0118.html b/docs/sfs/umn/sfs_01_0118.html index 7e380c904..c059c2281 100644 --- a/docs/sfs/umn/sfs_01_0118.html +++ b/docs/sfs/umn/sfs_01_0118.html @@ -3,11 +3,11 @@--Parent topic: Data Migration-Failed to Create an SFS Turbo File System
-Symptom
An SFS Turbo file system fails to be created.
Fault Diagnosis
The following fault causes are sequenced based on their occurrence probability.
+Troubleshooting
Possible causes are described here in order of how likely they are to occur.
If the fault persists after you have ruled out one cause, move on to the next one in the list.
-Figure 1 Fault diagnosis+
Figure 1 Troubleshooting-Table 1 Fault diagnosis Possible Cause
+Table 1 Troubleshooting Possible Cause
Solution
The quota is insufficient.
The number of created file systems has reached the upper limit. to increase the quota.
+The number of created file systems has reached the upper limit. Apply for a higher quota.
The subnet does not have sufficient IP addresses.
@@ -25,7 +25,7 @@The background resources are insufficient.
Background resources, such as compute and storage resources, have reached the upper limit. for technical consultation.
+Background resources, such as compute and storage resources, have reached the upper limit. Seek for technical consultation.
Before you start, understand the following concepts.
-NFS
Network File System (NFS) is a distributed file system protocol that allows different computers and operating systems to share data over a network.
File System
A file system provides users with shared file storage service through NFS. It is used for accessing network files remotely. After a user creates a file system on the console, the file system can be mounted to multiple servers and is accessible through the standard POSIX.
+File System
A file system provides users with shared file storage through NFS. It is used for accessing network files remotely. After you create a file system on the console, you can mount the file system on multiple cloud servers and access the file system from the servers through the standard POSIX.
diff --git a/docs/sfs/umn/sfs_01_0125.html b/docs/sfs/umn/sfs_01_0125.html index 3ebdc4271..a62b84d3e 100644 --- a/docs/sfs/umn/sfs_01_0125.html +++ b/docs/sfs/umn/sfs_01_0125.html @@ -7,7 +7,7 @@POSIX
Portable Operating System Interface (POSIX) is a set of interrelated standards specified by Institute of Electrical and Electronics Engineers (IEEE) to define the application programming interface (API) for software compatible with variants of the UNIX operating system. POSIX is intended to achieve software portability at the source code level. That is, a program written for a POSIX compatible operating system may be compiled and executed on any other POSIX operating system.
-Fault Diagnosis
Check whether the port of the target server is enabled and correctly configure the port on the security group console.
Solution
- Log in to the ECS console.
- Log in to the management console.
- Click
in the upper left corner and select your desired region and project. - Under Compute, choose Elastic Cloud Server.
-Solution
- Log in to the ECS console.
- Log in to the management console.
- Click
in the upper left corner and select your desired region and project. - Under Compute, choose Elastic Cloud Server.
- In the navigation pane on the left, choose Elastic Cloud Server. On the page displayed, select the target server. Go to the server details page.
- Click the Security Groups tab and select the target security group. Click Manage Rule to go to the security group console.
- On the displayed page, click the Inbound Rules tab and click Add Rule. The Add Inbound Rule page is displayed. Add rules as follows:
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.
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 section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. In 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.
diff --git a/docs/sfs/umn/sfs_01_0134.html b/docs/sfs/umn/sfs_01_0134.html index 503cdfa4a..b1a9d55c4 100644 --- a/docs/sfs/umn/sfs_01_0134.html +++ b/docs/sfs/umn/sfs_01_0134.html @@ -5,13 +5,13 @@Before mounting a general purpose file system to a compute resource, you need to create a VPC endpoint in the region where the compute resource belongs.
VPC endpoints are not required for SFS Capacity-Oriented and SFS Turbo file systems.
Prerequisites
- Before creating a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
+Prerequisites
- Before creating a general purpose file system, ensure that a VPC is available.
If no VPC is available, create one by referring to section "Creating a VPC" in the Virtual Private Cloud User Guide.
- Before creating a general purpose file system, ensure that ECSs are available and in the created VPC.
If no ECS is available, create ECSs by referring to "Creating an ECS" in the Elastic Cloud Server User Guide.
Procedure
- Log in to the console.
- Log in to the management console.
- Click in the upper left corner and select your desired region and project.
- Choose Networking > VPC Endpoint > VPC Endpoints.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
-Figure 1 Create VPC Endpoint+Figure 1 Create VPC Endpoint - Set the parameters as prompted.-
Table 1 Parameters for purchasing an endpoint Parameter
Figure 1 shows the process for creating and mounting an SFS Turbo file system.
Figure 2 shows the process for creating and mounting an SFS Capacity-Oriented file system.
Figure 3 shows the process for creating and mounting a general purpose file system.
- - - + + +diff --git a/docs/sfs/umn/sfs_01_0334.html b/docs/sfs/umn/sfs_01_0334.html index b8de606de..4a38cb29b 100644 --- a/docs/sfs/umn/sfs_01_0334.html +++ b/docs/sfs/umn/sfs_01_0334.html @@ -3,9 +3,11 @@Managing SFS Turbo+OBS Storage Interworking
-Overview
In scenarios like AI training and inference, high-performance data preprocessing, EDA, rendering, and simulation, you can use SFS Turbo file systems to speed access to your data in OBS buckets. After binding a directory in your file system with an OBS bucket, you can synchronize data between the file system and bucket through import and export tasks. You can enjoy the following benefits from SFS Turbo file caching: Before starting upper-layer training tasks, you can preload data in your OBS bucket to an SFS Turbo file system to speed up data access. Intermediate data and result data generated from upper-layer tasks is written to SFS Turbo file systems at a high speed. Downstream services can read and process the intermediate data, and you can asynchronously export the result data to OBS buckets for long-term low-cost storage. In addition, SFS Turbo allows you to configure a cache data eviction duration to delete data that has not been accessed for a long time to free up the cache space.
Notes and Constraints
- SFS Turbo file system types that support storage interworking: 250 MB/s/TiB, 125 MB/s/TiB, 40 MB/s/TiB, and 20 MB/s/TiB
- After you have configured storage interworking between OBS and a directory in SFS Turbo, operations like creating hard links, configuring directory quota limits, and renaming are no longer supported.
- You can configure a maximum of 16 interworking directories for a single SFS Turbo file system.
- Adding OBS buckets as storage backends depends on the OBS service, so you must have the OBS Administrator permissions.
- Files and directories with the same name cannot coexist in directories of the same level.
- The maximum supported path length is 1,023 characters.
- For import tasks, the length of a file or subdirectory name cannot exceed 255 bytes.
- If an OBS bucket has WORM enabled, you can only import data from OBS to SFS Turbo, but cannot export data from SFS Turbo to OBS.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
-Constraints
- SFS Turbo file system types that support storage interworking: 250 MB/s/TiB, 125 MB/s/TiB, 40 MB/s/TiB, and 20 MB/s/TiB
- After you have configured storage interworking between OBS and a directory in SFS Turbo, operations like creating hard links, configuring directory quota limits, and renaming are no longer supported.
- You can configure a maximum of 16 interworking directories for a single SFS Turbo file system.
- Adding OBS buckets as storage backends depends on the OBS service, so you must have the OBS Administrator permissions.
- Files and directories with the same name cannot coexist in directories of the same level.
- The maximum supported path length is 1,023 characters.
- For import tasks, the length of a file or subdirectory name cannot exceed 255 bytes.
- If an OBS bucket has WORM enabled, you can only import data from OBS to SFS Turbo, but cannot export data from SFS Turbo to OBS.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
Adding an OBS Bucket
- Log in to the SFS console.
- In the file system list, click the name of the desired file system to go to its details page.
- On the Storage Backends tab, click Add OBS Bucket.Figure 1 Add OBS Bucket+
@@ -78,17 +80,17 @@Adding an OBS Bucket
+- Access the SFS Turbo file system list page.
- In the file system list, click the name of the desired file system to go to its details page.
- On the Storage Backends tab, click Add OBS Bucket.Figure 1 Add OBS Bucket+
- On the displayed Add OBS Bucket page, configure the following parameters.
- - Select "Grant SFS Turbo the read/write permissions on the OBS bucket using a bucket policy" and click OK.
- Select "Grant SFS Turbo the read/write permissions on the OBS bucket using a bucket policy" and click OK.
- OBS buckets configured with server-side encryption and OBS parallel file systems cannot be added as storage backends.
- When you add an OBS bucket as the storage backend, a bucket policy will be automatically created for the bucket, with the policy Sid set to PolicyAddedBySFSTurbo. Do not modify or delete this policy, or the interworking function cannot work normally.
- If you have added an OBS bucket as the storage backend for one or multiple SFS Turbo file systems, before you delete any file system or remove the bucket, do not delete the bucket. Otherwise, the interworking function cannot work normally.
- New: Files created and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
- Changed: Files previously imported from the OBS bucket and then modified in the SFS Turbo interworking directory. Any data or metadata modifications made will be automatically synchronized to the OBS bucket.
- Deleted: Files deleted from the SFS Turbo interworking directory. Deletions will be automatically synchronized to the OBS bucket, and only such files that were previously exported to the bucket will be deleted.
To configure auto synchronization when adding an OBS bucket, see Adding an OBS Bucket.
To configure auto synchronization after an OBS bucket is added, perform the following steps:
-- Find the added OBS bucket and click Auto Synchronization in the Operation column.Figure 2 Auto Synchronization-
- Configure Auto Export.Figure 3 Auto Export+
- Find the added OBS bucket and click Auto Synchronization in the Operation column.Figure 2 Auto Synchronization+
- Configure Auto Export.Figure 3 Auto Export
- Enable or disable auto export.
- If auto export is disabled, this function is not supported. After auto export is enabled, select the types of data to be exported. Supported types include New, Changed, and Deleted. For more information, see Table 1.
- Click OK.
- Find the added OBS bucket and click Auto Synchronization in the Operation column.
Metadata Import
After you add an OBS bucket as a storage backend, you can use the metadata import function.
-Before using an SFS Turbo file system to access data in your OBS bucket, you need to use metadata import to import the object metadata (name, size, last modification time) from the bucket to the file system. You can only access the object data in the interworking directory after the metadata is imported. This operation only imports the metadata. The data will be loaded from the bucket and cached in the file system when it is accessed for the first time. When the same data is accessed later, it will be accessed from the cache, instead of the bucket.
+Before accessing data in your OBS bucket from SFS Turbo, you need to use metadata import to import the object metadata (name, size, and last modification time) from the bucket to the file system. You can only access the object data in the interworking directory after the metadata is imported. This operation only imports the metadata. The data will be loaded from the bucket and cached in the file system when it is accessed for the first time. When the same data is accessed later, it will be accessed from the cache, instead of the bucket.
SFS Turbo supports two metadata import methods: quick import and additional metadata import. After the metadata import is complete, you can view the imported directories and files in the interworking directory.
-- Quick import: Use quick import if data in the bucket has not been exported from SFS Turbo before. A quick import only imports the object metadata (name, size, last modification time). After the import is complete, SFS Turbo will, by default, generate the additional metadata (uid, gid, directory permissions, and file permissions). If you want to specify the permissions of imported directories and files, follow the instructions in section "Creating a Data Import or Export Task" in the Scalable File Service API Reference. Such an operation is only valid for the current task. Quick import is faster, so you are advised to use quick import.
- Additional metadata import: Use additional metadata import if data in the bucket has been exported from SFS Turbo before. With additional metadata import, both the object metadata (name, size, last modification time) and the additional metadata (uid, gid, mode) will be imported. If there is no additional metadata, the permissions you specified will be used for imported directories and files.
- Find the added OBS bucket and click Import Metadata in the Operation column.Figure 4 Import Metadata+
- Quick import: Use quick import if data in the bucket has not been exported from SFS Turbo before. A quick import only imports the object metadata (name, size, and last modification time). After the import is complete, SFS Turbo will, by default, generate the additional metadata (uid, gid, directory permissions, and file permissions). If you want to specify the permissions of imported directories and files, follow the instructions in section "Creating a Data Import or Export Task" in the Scalable File Service API Reference. Such an operation is only valid for the current task. Quick import is faster, so you are advised to use quick import.
- Additional metadata import: Use additional metadata import if data in the bucket has been exported from SFS Turbo before. With additional metadata import, both the object metadata (name, size, and last modification time) and the additional metadata (uid, gid, and mode) will be imported. If there is no additional metadata, the permissions you specified will be used for imported directories and files.
- Find the added OBS bucket and click Import Metadata in the Operation column.Figure 4 Import Metadata
- Set Object Prefix to the prefix of objects in the OBS bucket. It can be a specific object name. To import metadata of all the objects in the OBS bucket, leave the prefix field empty.
- Select Import Additional Metadata to import additional metadata. If this option is not selected, the system will perform a quick import.
- Click OK.
@@ -96,7 +98,7 @@ - After you import data from OBS to SFS Turbo, if new data is written to the bucket or existing data is modified, you need to import the data to SFS Turbo again.
- The length of a file or subdirectory name cannot exceed 255 bytes.
Data Import
After you add an OBS bucket as a storage backend, you can use the data import function.
After a metadata import, data is not imported to the SFS Turbo file system. Instead, data will be loaded from the bucket to the file system when a file is accessed for the first time, which may take a long time. If your workloads are latency-sensitive and you know which directories and files need to be accessed, for example, AI training involves a large number of small files and is sensitive to latency, you can import specified directories and files in advance.
During a data import, both data and metadata will be imported, and a quick metadata import will be performed, meaning that the additional metadata (such as uid, gid, and mode) will not be imported. If you want to specify the permissions of imported directories and files, follow the instructions in section "Creating a Data Import or Export Task" in the Scalable File Service API Reference. Such an operation is only valid for the current task.
-- Find the added OBS bucket and click Data import in the Operation column.Figure 5 Data import+
- Find the added OBS bucket and click Data import in the Operation column.Figure 5 Data import
- Set Object Path to the path of objects in the OBS bucket (excluding the bucket name).
If you enter the path of a directory, end it with a slash (/).
- To import data of all the objects in the OBS bucket, leave the object path field empty. SFS Turbo will import data to the interworking directory and ensure that the file paths in the interworking directory are the same as those in the OBS bucket.
- Object path examples: (/mnt/sfs_turbo is the local mount point and output-1 is the interworking directory name.)
- If you enter dir/ as the object path, data will be imported to /mnt/sfs_turbo/output-1/dir.
- If you enter dir/file as the object path, data will be imported to /mnt/sfs_turbo/output-1/dir/file.
- If you leave the object path field empty, data will be imported to /mnt/sfs_turbo/output-1.
Data Export
After you add an OBS bucket as a storage backend, you can use the data export function.
Data export allows you to export to the OBS bucket the files newly created in the interworking directory or the objects previously imported and then modified in the interworking directory. You can specify a prefix for data export. Then, only directories and files that match the specified prefix will be exported to the bucket.
-- Find the added OBS bucket and click More > Export in the Operation column.Figure 6 Export+
- Find the added OBS bucket and click More > Export in the Operation column.Figure 6 Export
- Set File Prefix to the path of directories or files (excluding the interworking directory name) or that of a specific file. To export all files in the interworking directory to the bucket, leave the file prefix field empty.
- Click OK.
- Before data is exported, SFS Turbo starts asynchronous tasks to scan the files in the target directories. If there is any file that has been updated in the last 10 seconds, this file will not be exported.
- For a given file, if no changes were made since the last time it was exported to OBS, it will not be exported in the next export task even if the previously exported file has been deleted from the OBS bucket.
- After files are exported to OBS, any SFS Turbo metadata with a name starting with x-obs-meta-sfsturbo-st- will be included in the objects' custom metadata.
- The maximum file path that supports export is 1,023 characters.
- The maximum file size supported in an SFS Turbo file system is 320 TB, and the maximum file size that can be exported is 48.8 TB.
- When large files are exported, temporary files generated during the export will be stored in the x-obs-upload-sfsturbo-temp-part directory in the bucket. After the export is complete, SFS Turbo will automatically delete this directory as well as the temporary files in it.
- When a file is exported from SFS Turbo to OBS:
If it was previously imported to and then modified in SFS Turbo, it will overwrite its peer object in the bucket if it is newer. Otherwise, it will not overwrite its peer object in the bucket.
If you upload an object to OBS when an object with the same name is being exported, the object you uploaded may be overwritten.
@@ -118,24 +120,24 @@Evicting data by time
After adding an OBS bucket, you can configure a cold data eviction duration to delete data from the cache by time. Files that have not been accessed within the specified duration will be evicted.
The procedure is as follows:
-- Log in to the SFS console.
- In the file system list, click the name of the created SFS Turbo file system to go to its details page.
- On the Basic Info tab, configure a cold data eviction duration.Figure 7 Setting a cold data eviction duration+
- Access the SFS Turbo file system list page.
- In the file system list, click the name of the created SFS Turbo file system to go to its details page.
- On the Basic Info tab, configure a cold data eviction duration.Figure 7 Setting a cold data eviction duration
Evicting data by capacity
SFS Turbo file systems also support data eviction by capacity.
When the capacity usage of a file system reaches 95%, SFS Turbo will delete data that has not been accessed in the last 30 minutes until the capacity usage falls below 85%.
- - Data can be evicted by time or capacity depending on which rule is triggered first.
- Cold data eviction is enabled by default, and the default duration is 60 hours. To configure a cold data eviction duration by calling the API, see section "Updating a File System" in the Scalable File Service API Reference.
- Services will be affected if the capacity of an SFS Turbo file system is used up, so you are advised to configure an alarm rule on Cloud Eye to monitor the file system capacity usage.
- When a file system capacity alarm is generated, change the cold data eviction duration to a shorter one, for example from 60 hours to 40 minutes to speed up data eviction, or simply expand the file system capacity.
- Data can be evicted by time or capacity depending on which rule is triggered first.
- Cold data eviction is enabled by default, and the default duration is 60 hours. To configure a cold data eviction duration by calling the API, see section "Updating a File System" in the Scalable File Service API Reference.
- Services will be affected if the capacity of an SFS Turbo file system is used up, so you are advised to configure an alarm rule on Cloud Eye to monitor the file system capacity usage.
- When a file system capacity alarm is generated, change the cold data eviction duration to a shorter one, for example, from 60 hours to 40 minutes, to speed up data eviction, or simply expand the file system capacity.
- In high-performance scenarios, you are advised to configure a relatively long eviction duration to avoid the high latency caused by frequently loading data from OBS.
-Task Status
When you export data, a task record will be generated. You can view the task progress and status.
- The system retains the latest 1,000 task records. Earlier records will be deleted automatically.
- Above the storage backend list, click View Task Status.
- View the task records about export tasks. Click
to the right of the status to view the number of failures or success times. - In the search box in the upper right corner, enter the status, type, or creation time to filter tasks.
- Above the storage backend list, click View Task Status.
- View the task records about export tasks. Click to the right of the status to view the number of failures or successful executions.
- In the search box in the upper right corner, enter the status, type, or creation time to filter tasks.
FAQs
- In what cases will SFS Turbo evicts data?
For the files imported from OBS to SFS Turbo, if they not accessed within the configured eviction duration, they will be evicted.
+FAQs
- In what cases will SFS Turbo evict data?
For the files imported from OBS to SFS Turbo, if they are not accessed within the configured eviction duration, they will be evicted.
For the files created in SFS Turbo, they will only be evicted when they have been exported to OBS and meet the eviction rule. If they have not been exported, they will not be evicted.
- How do I import evicted data to my SFS Turbo file system?
- File data is loaded from the bucket to the file system when the file is read or written.
- You can use the data import function to manually load data to the file system.
- In what scenarios will data import fail?
When the SFS Turbo file system contains only the file metadata (only metadata is imported or data eviction happens) and the object in the OBS bucket has been deleted, importing data or access the file will fail.
+ - In what scenarios will data import fail?
When the SFS Turbo file system contains only the file metadata (only metadata is imported or data eviction happens) and the object in the OBS bucket has been deleted, importing data or accessing the file will fail.
- Are the import or export tasks synchronous or asynchronous?
Tasks are asynchronous. After a task is submitted, you can query the task status based on the task ID.
- If I delete the files in the SFS Turbo interworking directory, will the objects in the OBS bucket be deleted as well?
If auto synchronization is disabled, the answer is no. If auto synchronization is enabled, the answer is yes.
- In what cases will SFS Turbo evict data?
- Find the added OBS bucket and click More > Export in the Operation column.
- Find the added OBS bucket and click Data import in the Operation column.
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.
+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
@@ -46,7 +46,7 @@Maximum capacity of the file system
Encrypted
+Encryption
Encryption status of the file system. The value can be Yes or No.
- Click the name of a file system to view detailed information about the file system.Figure 1 Basic information of an SFS Capacity-Oriented file system-
Figure 2 Details of a general purpose file system-
Figure 3 Details of an SFS Turbo file system+
- Click the name of a file system to view detailed information about the file system.Figure 1 Basic information of an SFS Capacity-Oriented file system+Figure 2 Basic information of a general purpose file system+Figure 3 Basic information of an SFS Turbo file system
- (Optional) Search for the specified file system by file system name.You can search for SFS Capacity-Oriented file systems by tag in the upper right area above the file system list.
- 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 20 tags can be added at a time. - You can click Reset under the search criteria to reset.
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
- Log in to the SFS console.
- 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 above the file system list. In the displayed dialog box, confirm the information and then click OK. Batch deletion is only supported for SFS Capacity-Oriented file systems.
- - In the displayed dialog box for an SFS Turbo file system, as shown in Figure 1, confirm the information, enter DELETE in the text box, and click OK.
In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click OK.
- Only file systems whose statuses are Available or Creation failed can be deleted.
+Procedure
- Log in to the SFS console.
- 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 above the file system list. In the displayed dialog box, confirm the information and then click OK. Batch deletion is only supported for SFS Capacity-Oriented file systems.
+ - In the displayed dialog box for an SFS Turbo file system, confirm the information, enter DELETE in the text box, and click OK.
In the displayed dialog box for an SFS Capacity-Oriented or a general purpose file system, confirm the information and click OK.
+ - Check that the file system disappears from the file system list.
Mounting a File System Times Out
-Symptom
When a file system is mounted to servers using the mount command, message timed out is displayed.
+-Symptom
When a file system was mounted to a cloud server using the mount command, message timed out was returned.
diff --git a/docs/sfs/umn/sfs_01_1001.html b/docs/sfs/umn/sfs_01_1001.html deleted file mode 100644 index 9c3301996..000000000 --- a/docs/sfs/umn/sfs_01_1001.html +++ /dev/null @@ -1,200 +0,0 @@ - - -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 that mounts the file system runs Ubuntu18 or later.
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 mount fails. This issue will not occur on SFS Turbo file systems.
- Cause 4: The server that mounts the file system 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.
- 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 mount is successful, 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 mount fails.
- 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, 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.
- 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+
- 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 DNSThe 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. + -
- Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
- 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. +
- Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
- By default, the server inherits the DNS configuration of the VPC every time the server restarts. Changing only the server DNS configuration does not resolve 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. - -
- (Optional) Restart the server.
- 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.
- (Optional) Restart the server.
- Run the mount command again.
- If the mount is successful, no further action is required.
- If the problem persists, see the solution for cause 4.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
- Reconfigure DNS by referring to Configuring DNS.
- Check whether the target server running Ubuntu18 or later uses a private image. -
- Convert the public image server to a private image server.
- To create a private image based on an existing ECS, see section "Creating an Image" in the Elastic Cloud Server User Guide.
- Use the private image created in 3.a to create an ECS or change the ECS OS. For details, see section "Changing the OS" in the Elastic Cloud Server User Guide.
- Log in to the server and mount the file system again.
- Cause 4: The server that mounts the file system runs Ubuntu18 or later.
- Reconfigure DNS by referring to Configuring DNS.
- Check whether the server running Ubuntu18 or later was created from a private image. +
- Convert the public image server to a private image server.
- Create a private image for the server by referring to section "Creating an Image" in the Elastic Cloud Server User Guide.
- Use the private image obtained in 3.a to create a server or change the server OS to the created private image by referring to section "Changing the OS" in the Elastic Cloud Server User Guide.
- Log in to the server and remount the file system.
- Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
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.
-General purpose file systems cannot be mounted to 32-bit Linux servers.
--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.
-Constraints
- This constraint only applies to local paths (mount points) and does not affect other files or directories.
-Metadata of the local paths (mount points) cannot be modified. Specifically, the following operations cannot be performed on the local paths' metadata:
-- touch: Update file access time and modification time.
-- rm: Delete files or directories.
-- cp: Replicate files or directories.
-- mv: Move files or directories.
-- rename: Rename files or directories.
-- chmod:Modify permissions on files or directories.
-- chown: Change file or directory owners.
-- chgrp: Change file or directory groups.
-- ln: Create hard links.
-- link: Create hard links.
-- unlink: Delete hard links.
-The atime, ctime, and mtime attributes of a local path (root directory of the mount point) are the current time. So each time the root directory attribute is queried, the current time of the server is returned.
--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 go to the ECS console.
- 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.
- - Install the NFS client.
- Install the NFS client.
- Run the following command to check whether the NFS software package is installed.
- In CentOS, Red Hat, Oracle Enterprise Linux, SUSE, EulerOS, Fedora, or OpenSUSE: -
- In Debian or Ubuntu: -
If a command output similar to the following is displayed, the NFS software package has been installed and you can go to 4. If no such command output is displayed, go to b.-- In CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
libnfsidmap -nfs-utils
- - In SUSE or OpenSUSE:
nfsidmap -nfs-client
- - In Debian or Ubuntu:
nfs-common
-
- 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.
-
- Run the following command to check whether the NFS software package is installed.
- Install the NFS client.
- 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.example.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.
- 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.)
- - 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,tcp Mount point Local path
-To mount a general purpose file system, run the following command: mount -t nfs -o vers=3,timeo=600,nolock,proto=tcp Mount point Local path
-- General purpose file systems do not support the noresvport mount option.
-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.
-noresvport
-Whether the NFS client uses a new TCP port when a network connection is re-established.
-It is strongly recommended you use the noresvport option, which ensures that your file system maintains uninterrupted availability after a network reconnection or recovery.
-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.
-proto
-Protocol used by NFS clients to send requests to the server. Both UDP and TCP protocols can be used.
-UDP is currently not supported by general purpose file systems. If you are using general purpose file systems, set this option to tcp, that is, proto=tcp.
-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:/.
-Figure 1 shows an example.
-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.
-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. Recommended value: 1
-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.
-noresvport
-Whether the NFS client uses a new TCP port when a network connection is re-established.
-It is strongly recommended you use the noresvport option, which ensures that your file system maintains uninterrupted availability after a network reconnection or recovery.
-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.
- - 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=)
- - 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.
-
-- - - \ No newline at end of file diff --git a/docs/sfs/umn/sfs_03_0036.html b/docs/sfs/umn/sfs_03_0036.html new file mode 100644 index 000000000..507330eb7 --- /dev/null +++ b/docs/sfs/umn/sfs_03_0036.html @@ -0,0 +1,38 @@ + + +--Parent topic: Mount a File System-Migrating Data from SFS Capacity-Oriented to Other File Systems Using rclone
+++Solution Overview
You can migrate data from SFS Capacity-Oriented to General-Purpose File System or SFS Turbo.
+In this solution, a Linux ECS is used to connect the SFS Capacity-Oriented file system and the destination file system.
++Constraints
- Only Linux ECSs can be used for data migration.
- The Linux ECS, SFS Capacity-Oriented file system, and destination file system must be in the same VPC. If the destination file system is a general-purpose file system, you need to configure a VPC endpoint.
- Incremental migration is supported, so you can only migrate the changed data.
+Prerequisites
- You have created a Linux ECS.
- You have created an SFS Capacity-Oriented file system and a destination file system and have obtained their mount points.
+Procedure
- Log in to the ECS console.
- Log in to the created Linux ECS, which can access both the SFS Capacity-Oriented and the destination file systems.
- Mount the SFS Capacity-Oriented file system, which is file system 1 in this example.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock <mount-point-of-file-system-1> /mnt/src
+ - Mount the general-purpose file system or SFS Turbo file system, which is file system 2 in this example.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock <mount-point-of-file-system-2> /mnt/dst
+ - Install rclone on the Linux ECS.
wget https://downloads.rclone.org/v1.53.4/rclone-v1.53.4-linux-amd64.zip --no-check-certificate +unzip rclone-v1.53.4-linux-amd64.zip +chmod 0755 ./rclone-*/rclone +cp ./rclone-*/rclone /usr/bin/ +rm -rf ./rclone-*
++ rclone does not retain the file permissions or owner group information on the source. Use rsync if you have such requirements.
+ - Synchronize data to the destination file system.
rclone copy /mnt/src /mnt/dst -P --transfers 32 --checkers 64 --links --create-empty-src-dirs
++ The parameters are described as follows. Set transfers and checkers based on the system specifications.
+- /mnt/src: source path
- /mnt/dst: destination path
- --transfers: number of files that can be transferred concurrently
- --checkers: number of local files that can be scanned concurrently
- -P: data copy progress
- --links: replicates the soft links from the source. They are saved as soft links in the destination.
- --copy-links: replicates the content of files to which the soft links point. They are saved as files rather than soft links in the destination.
- --create-empty-src-dirs: replicates the empty directories from the source to the destination.
After data synchronization is complete, go to the destination file system to check whether data is migrated.
+
+Verification
- Log in to the Linux ECS.
- Check the file synchronization results on the destination server.
cd /mnt/dst +ls | wc -l
+If the data volume is the same as that on the source server, data is migrated successfully.
+
++ diff --git a/docs/sfs/umn/sfs_03_0037.html b/docs/sfs/umn/sfs_03_0037.html new file mode 100644 index 000000000..f918f1ed8 --- /dev/null +++ b/docs/sfs/umn/sfs_03_0037.html @@ -0,0 +1,55 @@ + + +++Parent topic: Data Migration+Migrating Data from SFS Capacity-Oriented to General-Purpose File System Using fpart
+++Solution Overview
This section describes how to use fpart to migrate data from SFS Capacity-Oriented to General-Purpose File System. The migration aims to efficiently and securely migrate data while ensuring data integrity and consistency. The entire process includes a full migration (no impact on services), a first incremental migration (no impact on services), unmounting the SFS Capacity-Oriented file system (services are interrupted), a second incremental migration (services are interrupted), and changing the mount point (services are interrupted).
++Constraints
- This solution is only applicable for the data migration using Linux ECSs.
- This solution is not applicable for SFS Capacity-Oriented file systems using CIFS or those mounted on Windows clients.
- The Linux ECS, SFS Capacity-Oriented file system, and general-purpose file system must be in the same VPC.
- If the general-purpose file system is used by a CCE cluster, the CCE cluster must be upgraded to version 1.19.10, and the everest add-on version must be later than 2.0.9.
+Solution Architecture
Figure 1 Process of migrating data from SFS Capacity-Oriented to General-Purpose File System using fpart+
+Preparations
- Create a general-purpose file system in the VPC where the SFS Capacity-Oriented file system resides. If no VPC is available, create one in the same region and then create the general-purpose file system. For how to create a VPC, see section "Creating a VPC with a Subnet" in the Virtual Private Cloud User Guide.
- Buy a VPC endpoint (used for free) in the desired VPC.
- If a Linux ECS is available, skip this step. If not, buy a Linux ECS. You are advised to buy an ECS with 8 or 16 vCPUs. This ECS must be in the VPC where the SFS Capacity-Oriented file system and general-purpose file system belong and can communicate with the file systems.
- Install fpart on the Linux ECS.
yum -y install fpart rsync
+ - Create two local mount points on the Linux ECS.
mkdir /mnt/src
+mkdir /mnt/dst
+ - Obtain the mount points of the SFS Capacity-Oriented file system and general-purpose file system from the console. Then, mount the file systems on the created local mount points (/mnt/src and /mnt/dst).
mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-SFS-Capacity-Oriented-file-system> /mnt/src
+mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-general-purpose-file-system> mnt/dst
+ - If the mount fails, install the required tool package by referring to section "Mounting an NFS File System to ECSs (Linux)" in the Scalable File Service Getting Started.
+ +Procedure
- Full migration: Migrate all files from the SFS Capacity-Oriented file system to the general-purpose file system.
- Log in to the ECS using VNC and run the following command to synchronize data:
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++ - n: the number of parallel copy threads
- f: the number of files each thread can copy
- o: the rsync configuration option
- v: the output detailed logs
- If there are a large number of files, you can run the command concurrently for the subdirectories in /mnt/src.
- You can adjust the n and f options based on the file and directory structure.
- The default run log files are stored in /tmp/fpsync, under which log stores task run logs, parts stores file partition logs, queue stores execution configurations, and work stores the copy commands. A run ID is returned after you run the fpsync command. You can use this run ID to check the task running status.
- Log in to the ECS using VNC and run the following command to synchronize data:
- First incremental migration: If there is data written to the source files from the service application during the full migration, synchronize the incremental data after the full migration is complete.Run the following command to perform an incremental migration:+
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++
Take note of the start time and end time of this operation. This period is approximately equal to how long customer services need to be stopped in the following steps.
+ - Unmounting the SFS Capacity-Oriented file system: To prevent new data from being written to the file system, before synchronizing the incremental data, stop the service application that uses the source file system on all ECSs and containers.+
- Ensure that the SFS Capacity-Oriented file system is unmounted from all service ECSs (or cloud containers). Otherwise, after the migration, data in the general-purpose file system may be inconsistent with that in the SFS Capacity-Oriented file system.
- Do not unmount the SFS Capacity-Oriented file system from the ECS that you use to perform the migration.
- The operations vary in ECS and CCE scenarios. Refer to the operations based on your scenario.
- Ensure that services are stopped when you perform this step.
ECS scenario:
+- Log in to each service ECS that mounts the SFS Capacity-Oriented file system.
- Unmount the SFS Capacity-Oriented file system.
umount -f <local-mount-point>
+
- Second incremental migration: Synchronize the incremental data generated after the first incremental migration to the general-purpose file system. After the synchronization, data in the general-purpose file system will be the same as that in the SFS Capacity-Oriented file system.
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++ - Check that data in the general-purpose file system is the same as that in the SFS Capacity-Oriented file system.
- Ensure that services are stopped when you perform this step.
- Mounting the general-purpose file system: Switch the service to the general-purpose file system by mounting all service ECSs (or cloud containers) to the general-purpose file system.
ECS scenario:
+- Log in to the service ECS and run the following command to unmount the SFS Capacity-Oriented file system:
umount -f <local-mount-point>
+ - Mount the general-purpose file system.
mount -t nfs -o vers=3,timeo=600,noresvport,nolock <mount-point-of-the-general-purpose-file-system> <local-mount-point>
+
+ - Ensure that the mount parameters and directories are correct. Or, services may be affected.
- Log in to the service ECS and run the following command to unmount the SFS Capacity-Oriented file system:
- The customer restores services and checks whether services are normal.
- After observing the services for a period of time, the customer can release the SFS Capacity-Oriented file system resources to prevent unintended charges.
++ + + \ No newline at end of file diff --git a/docs/sfs/umn/sfs_03_0038.html b/docs/sfs/umn/sfs_03_0038.html new file mode 100644 index 000000000..a5f037a69 --- /dev/null +++ b/docs/sfs/umn/sfs_03_0038.html @@ -0,0 +1,53 @@ + + +++Parent topic: Data Migration+Migrating Data from SFS Capacity-Oriented to SFS Turbo Using fpart
+++Solution Overview
This section describes how to use fpart to migrate data from SFS Capacity-Oriented to SFS Turbo. The migration aims to efficiently and securely migrate data while ensuring data integrity and consistency. The entire process includes a full migration (no impact on services), a first incremental migration (no impact on services), unmounting the SFS Capacity-Oriented file system (services are interrupted), a second incremental migration (services are interrupted), and changing the mount point (services are interrupted).
++Constraints
- This solution is only applicable for the data migration using Linux ECSs.
- The Linux ECS, SFS Capacity-Oriented file system, and SFS Turbo file system must be in the same VPC.
- This solution is not applicable for SFS Capacity-Oriented file systems using CIFS or those mounted on Windows clients.
- If the SFS Turbo file system is used by a CCE cluster, the CCE cluster must be upgraded to version 1.15+, and the everest add-on version must be later than 1.1.13.
+Solution Architecture
Figure 1 Process of migrating data from SFS Capacity-Oriented to SFS Turbo using fpart+
+Preparations
- Create an SFS Turbo file system in the VPC where the SFS Capacity-Oriented file system resides. If no VPC is available, create one in the same region and then create the SFS Turbo file system. For how to create an SFS Turbo file system, see Creating an SFS Turbo File System. For details about how to create a VPC, see section "Creating a VPC with a Subnet" in the Virtual Private Cloud User Guide.
- If a Linux ECS is available, skip this step. If not, buy a Linux ECS. You are advised to buy an ECS with 8 or 16 vCPUs. This ECS must be in the VPC where the SFS Capacity-Oriented and SFS Turbo file systems belong and can communicate with the file systems.
- Install fpart on the Linux ECS.
yum -y install fpart rsync
+ - Create two local mount points on the Linux ECS.
mkdir /mnt/src
+mkdir /mnt/dst
+ - Obtain the mount points of the SFS Capacity-Oriented and SFS Turbo file systems from the console. Then, mount the file systems on the created local mount points (/mnt/src and /mnt/dst).
mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-SFS-Capacity-Oriented-file-system> /mnt/src
+mount -t nfs -o vers=3,timeo=600,nolock <mount-point-of-the-SFS-Turbo-file-system> /mnt/dst
+ - If the mount fails, install the required tool package by referring to section "Mounting an NFS File System to ECSs (Linux)" in the Scalable File Service Getting Started.
+Procedure
- Full migration: Migrate all files from the SFS Capacity-Oriented file system to the SFS Turbo file system.
- Log in to the ECS using VNC and run the following command to synchronize data:
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++ - n: the number of parallel copy threads
- f: the number of files each thread can copy
- o: the rsync configuration option
- v: the output detailed logs
- If there are a large number of files, you can run the command concurrently for the subdirectories in /mnt/src.
- You can adjust the n and f options based on the file and directory structure.
- The default run log files are stored in /tmp/fpsync, under which log stores task run logs, parts stores file partition logs, queue stores execution configurations, and work stores the copy commands. You can check the task running status based on these logs.
- Log in to the ECS using VNC and run the following command to synchronize data:
- First incremental migration: Synchronize the incremental data generated after the full migration to the SFS Turbo file system.
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++ Take note of the start time and end time of this operation. This period is approximately equal to how long customer services need to be stopped in the following steps.
+ - Unmounting the SFS Capacity-Oriented file system: To prevent new data from being written to the file system, before synchronizing the incremental data, stop the service application that uses the source file system on all ECSs and containers.+
- Ensure that the SFS Capacity-Oriented file system is unmounted from all service ECSs (or cloud containers). Otherwise, after the migration, data in the SFS Turbo file system may be inconsistent with that in the SFS Capacity-Oriented file system.
- Do not unmount the SFS Capacity-Oriented file system from the ECS that you use to perform the migration.
- The operations vary in ECS and CCE scenarios. Refer to the operations based on your scenario.
- Ensure that services are stopped when you perform this step.
ECS scenario:
+- Log in to each service ECS that mounts the SFS Capacity-Oriented file system.
- Unmount the SFS Capacity-Oriented file system.
umount -f <local-mount-point>
+
- Second incremental migration: Synchronize the incremental data generated after the first incremental migration to the SFS Turbo file system. After the synchronization, data in the SFS Turbo file system will be the same as that in the SFS Capacity-Oriented file system.
fpsync -n 500 -f 500 -o "-lptgoDvu --numeric-ids" -v /mnt/src/ /mnt/dst/
++ - Check that data in the SFS Turbo file system is the same as that in the SFS Capacity-Oriented file system.
- Ensure that services are stopped when you perform this step.
- Mounting the SFS Turbo file system: Switch the service to the SFS Turbo file system by mounting all service ECSs (or cloud containers) to the SFS Turbo file system.
ECS scenario:
+- Log in to the service ECS and run the following command to unmount the SFS Capacity-Oriented file system:
umount -f <local-mount-point>
+ - Mount the SFS Turbo file system.
mount -t nfs -o vers=3,nolock <mount-point-of-the-SFS-Turbo-file-system>
+
+ - Ensure that the mount parameters and directories are correct. Or, services may be affected.
- Log in to the service ECS and run the following command to unmount the SFS Capacity-Oriented file system:
- The customer restores services and checks whether services are normal.
- After observing the services for a period of time, the customer can release the SFS Capacity-Oriented file system resources to prevent unintended charges.
++ + + \ No newline at end of file++Parent topic: Data Migration+
- Before creating a general purpose file system, ensure that a VPC is available.
- (Optional) In a network environment that uses the DHCP server, edit the /etc/resolv.conf file to prevent the file from being automatically modified upon an ECS restart, and prevent the DNS server IP address added in 2 from being reset.
- Run the following command to lock the file:
- Run the following command to add a software repository.
- Run the following command to add a software repository. This step uses opensuse12.2 as an example.
- Run the following command to check whether a software repository has been enabled.
- Log in to the management console using a cloud account.
Mounting a File System Automatically
-File system mounting information may be lost after a server is restarted. You can configure automatic mounting for the server to avoid the mounting information loss.
-Restrictions
Because the service startup sequences in different operating systems vary, some servers running CentOS may not support the following automatic mounting schemes. In this case, manually mount the file system.
+File system mount information may be lost after a server is restarted. You can configure auto mount on the server to avoid losing the mount information.
+-Restrictions
Because service startup sequences in different OSs vary, some servers running CentOS may not support the following auto mount plan. In this case, manually mount the file system.
Procedure (Linux)
- Log in to the management console using a cloud account.
