Parameter
+Table 3 SFS Turbo file systemsParameter
|
-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
+ | 250 MB/s/TiB
|
Max. bandwidth
@@ -129,7 +165,7 @@
| Low latency and cost effectiveness
|
-Typical use cases
+ | Typical scenarios
|
Log storage, file sharing, content management, and websites.
|
@@ -144,20 +180,20 @@
Table 3 Previous-generation SFS Turbo file systemsParameter
+Table 4 Previous-generation SFS Turbo file systemsParameter
|
-Standard
+ | Standard
|
-Standard - Enhanced
+ | Standard-Enhanced
|
-Performance
+ | Performance
|
-Performance - Enhanced
+ | Performance-Enhanced
|
Max. bandwidth
|
-120 MB/s
+ | 120 MB/s
|
1 GB/s
|
@@ -207,10 +243,10 @@
Low latency, high IOPS, and tenant exclusive
|
-Low latency, high IOPS, high bandwidth, and tenant exclusive
+ | Low latency, high IOPS, high bandwidth, and tenant exclusive
|
-Typical use cases
+ | Typical scenarios
|
Code storage, file sharing, enterprise OA, and log storage.
|
@@ -224,13 +260,13 @@
 - In the table, the maximum IOPS and maximum bandwidth all include both the read and write operations. So, maximum IOPS = read IOPS + write IOPS.
- The expansion increment of SFS Turbo Standard, SFS Turbo Standard - Enhanced, SFS Turbo Performance, or SFS Turbo Performance - Enhanced file systems is 100 GB. The expansion increment of file systems with the 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB flavor is 1.2 TB.
- Maximum performance can be reached with multiple ECSs in parallel which have recommended configuration c4.4xlarge.4.
+ - In the table, the maximum IOPS and maximum bandwidth all include both the read and write operations. So, maximum IOPS = read IOPS + write IOPS.
- The expansion increment of SFS Turbo Standard, Standard - Enhanced, Performance, or Performance - Enhanced file systems is 100 GB. The expansion increment of 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file systems is 1.2 TB.
- Maximum performance can be reached with multiple ECSs in parallel which have recommended configuration c4.4xlarge.4.
File System Encryption
-SFS provides you with the encryption function. You can encrypt your data on the 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, you can use the key import function on KMS Console to create a customer master key (CMK) whose key material is empty, and import the key material to the CMK. 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. For SFS Turbo file systems, no authorization is required.
- Encryption KeyThe keys provided by KMS for SFS Capacity-Oriented file system encryption include a default master key and CMKs.
- - Default master key: SFS automatically creates a default master key and names it sfs/default.
The default master key cannot be disabled and does not support scheduled deletion.
- - CMKs: Existing or newly created CMKs. For details, see "Creating a CMK" in Key Management Service User Guide.
If the CMK used by the encrypted file system is disabled or planned to be deleted, the file system can only be used within a certain period of time (30s by default). Exercise caution in this case.
+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.
+ 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 KeyKeys 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.
+ - Custom keys: Existing or newly created custom keys. For details, see Creating a Custom Key in the Key Management Service User Guide.
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.
- An SFS Turbo file system does not have a default master key. You can use your existing key or create a new key. For details, see "Creating a CMK" in Key Management Service User Guide.
+ SFS Turbo file systems do not have default keys. You can use your existing key or create a key. For details, see section "Creating a Key" in the Key Management Service User Guide.
+ General Purpose File System does not support file system encryption.
Who Has the Rights to Encrypt File Systems?- The security administrator who has the "Security Administrator" permission can grant the KMS access rights for encryption.
- A common user who does not have the "Security Administrator" permission needs to contact the system administrator to obtain the "Security Administrator" permission.
As long as the KMS access rights have been granted to SFS Capacity-Oriented, all common users in the same region can directly use the encryption function.
@@ -17,7 +18,7 @@
diff --git a/docs/sfs/umn/sfs_01_0007.html b/docs/sfs/umn/sfs_01_0007.html
index bd455012..452e128a 100644
--- a/docs/sfs/umn/sfs_01_0007.html
+++ b/docs/sfs/umn/sfs_01_0007.html
@@ -10,11 +10,11 @@
|
-A file system and the servers must belong to the same project. File systems are mounted to shared paths for data sharing.
+ | A file system and the servers must belong to the same project so that they can mount the same file system for data sharing.
|
Elastic Cloud Server (ECS)
|
-Mounting an NFS File System to ECSs (Linux)
+ | Mounting an NFS File System to ECSs (Linux)
Mounting an NFS File System to ECSs (Windows)
|
@@ -26,6 +26,14 @@
Creating a File System
|
+VPCEP is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services. It allows you to plan networks flexibly without having to use EIPs.
+Communication between general purpose file systems and ECSs is established through VPC endpoints, so that ECSs can access file systems.
+ |
+VPC Endpoint (VPCEP)
+ |
+Configure a VPC Endpoint
+ |
+
IAM is an enterprise-level self-help cloud resource management system. It provides user identity management and access control functions. When an enterprise needs to provide SFS for multiple users within the enterprise, the enterprise administrator can use IAM to create users and control these users' permissions on enterprise resources.
|
Identity and Access Management (IAM)
@@ -61,7 +69,7 @@
diff --git a/docs/sfs/umn/sfs_01_0008.html b/docs/sfs/umn/sfs_01_0008.html
index db37c0ff..ff59b596 100644
--- a/docs/sfs/umn/sfs_01_0008.html
+++ b/docs/sfs/umn/sfs_01_0008.html
@@ -11,7 +11,7 @@
diff --git a/docs/sfs/umn/sfs_01_0011.html b/docs/sfs/umn/sfs_01_0011.html
index ffd2e833..8684e1a3 100644
--- a/docs/sfs/umn/sfs_01_0011.html
+++ b/docs/sfs/umn/sfs_01_0011.html
@@ -1,17 +1,22 @@
-Restrictions and Limitations
-General- SFS supports the NFSv3 protocol only. The default export options are rw, no_root_squash, no_all_squash, and sync.
- To obtain better performance, you are advised to use the operating systems listed in Supported Operating Systems, which have passed the compatibility test.
- Currently, SFS does not support replication.
- Currently, SFS does not support cross-region access.
- SFS Capacity-Oriented does not apply to file storage scenarios requiring low latency and high IOPS, such as database services, website building, and code storage.
+ Notes and Constraints
+ General- SFS supports the NFSv3 protocol only. The default export options are rw, no_root_squash, no_all_squash, and sync.
- Currently, SFS does not support replication.
- Currently, SFS does not support cross-region access.
- SFS Capacity-Oriented is not suitable for file storage scenarios requiring low latency and high IOPS, such as database services, website building, and code storage.
SFS Capacity-Oriented- SFS Capacity-Oriented can be accessed only on the intranet and used only on the cloud.
- - Currently, NFSv3 protocol 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.
+ - 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.
- 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 capacity of a single file is 16 TB.
- Maximum number of files supported by a single file system = Capacity/16 KB. 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 contains a maximum of 2 million files.
- The maximum full path is 1024 bytes, and the maximum file name length is 255 bytes.
- The maximum soft link length is 1024 bytes.
- The maximum number of hard links is 255.
- The maximum directory depth is 100 layers.
+ General Purpose File System
+
+ 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.
+
+ - 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.
diff --git a/docs/sfs/umn/sfs_01_0013.html b/docs/sfs/umn/sfs_01_0013.html
index db30a1c4..20d6de6a 100644
--- a/docs/sfs/umn/sfs_01_0013.html
+++ b/docs/sfs/umn/sfs_01_0013.html
@@ -1,14 +1,14 @@
Permissions
- If you need to assign different permissions to employees in your enterprise to access your SFS resources on the cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.
+ If you need to assign different permissions to employees in your enterprise to access your SFS resources on the cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
With IAM, you can use your cloud account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use SFS resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using SFS resources.
If your cloud account does not require individual IAM users for permissions management, skip this section.
- IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see Identity and Access Management User Guide.
+ IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see Identity and Access Management User Guide.
SFS PermissionsBy default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
SFS is a project-level service deployed and accessed in specific physical regions. To assign SFS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing SFS, the users need to switch to a region where they have been authorized to use this service.
You can grant users permissions by using roles and policies.
- - Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by SFS, see section "Permissions Policies and Supported Actions" in the Scalable File Service API Reference.
+ - Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by SFS, see section "Permissions Policies and Supported Actions" in the Scalable File Service API Reference.
Table 1 lists all the system-defined roles and policies supported by SFS Turbo.
Table 1 System-defined roles and policies supported by SFS TurboRole/Policy Name
|
@@ -42,11 +42,44 @@
|---|
+ Table 2 lists all the system-defined roles and policies supported by General Purpose File System.
+ Table 2 System-defined roles and policies supported by General Purpose File SystemRole/Policy Name
+ |
+Description
+ |
+Type
+ |
+Dependency
+ |
+
|---|
+
+Tenant Administrator
+ |
+Permissions to perform all operations on all services except IAM
+ |
+System-defined policy
+ |
+None
+ |
+
+Tenant Guest
+ |
+Permissions to perform read-only operations on all services except IAM
+ |
+System-defined policy
+ |
+None
+ |
+
+
+
+
+
diff --git a/docs/sfs/umn/sfs_01_0014.html b/docs/sfs/umn/sfs_01_0014.html
deleted file mode 100644
index 18b99b1d..00000000
--- a/docs/sfs/umn/sfs_01_0014.html
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
- Supported Operating Systems
- Table 1 lists the operating systems that have passed the compatibility test.
- Table 1 Supported operating systemsType
- |
-Version
- |
-
|---|
-
-CentOS
- |
-CentOS 5, 6, and 7 for x86
- |
-
-Debian
- |
-Debian GNU/Linux 6, 7, 8, and 9 for x86
- |
-
-Oracle
- |
-Oracle Enterprise Linux 5, 6, and 7 for x86
- |
-
-Red Hat
- |
-Red Hat Enterprise Linux 5, 6, and 7 for x86
- |
-
-SUSE
- |
-SUSE Linux Enterprise Server 10, 11, and 12 for x86
- |
-
-Ubuntu
- |
-Ubuntu 10, 11, 12, 13, 14, and 15 LTS for x86
- |
-
-EulerOS
- |
-EulerOS 2
- |
-
-Fedora
- |
-Fedora 24 and 25
- |
-
-OpenSUSE
- |
-OpenSUSE 42
- |
-
-Windows
- |
-Windows Server 2008, 2008 r2, 2012, 2012 r2, and 2016 for x64
-Windows 7, 8, and 10
- |
-
-
-
-
-
-
-
-
diff --git a/docs/sfs/umn/sfs_01_0024.html b/docs/sfs/umn/sfs_01_0024.html
index 7d9e62b4..b6fbfb46 100644
--- a/docs/sfs/umn/sfs_01_0024.html
+++ b/docs/sfs/umn/sfs_01_0024.html
@@ -1,14 +1,10 @@
-
- Mount a File System
-
-
-
+ Mount a File System
+
-- 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 281bf148..7108f2ad 100644
--- a/docs/sfs/umn/sfs_01_0025.html
+++ b/docs/sfs/umn/sfs_01_0025.html
@@ -5,44 +5,44 @@
RestrictionsBecause 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.
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.
- Under Computing, click Elastic Cloud Server to switch 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
+ - 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.
- - (Optional) Run the following command to view the updated content of the /etc/fstab file:
cat /etc/fstab
+ - (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.
-Figure 1 Updated file content
- - If the automatic mounting fails due to a network issue, add the sleep parameter and a time in front of the mounting 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 Mount point/local_path
+Figure 1 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
Field DescriptionTable 1 describes the mount fields.
- Table 1 Field descriptionField
+Table 1 Field descriptionField
|
-Description
+ | Description
|
|---|
-Mount point
+ | Mount point
|
-Mount object, that is, the mount point of the file system to be mounted. Set this parameter to the mount point in the mount command that is used in Mounting an NFS File System to ECSs (Linux).
+ | Mount object, that is, the mount point of the file system to be mounted. Set this parameter to the mount point in the mount command that is used in Mounting an NFS File System to ECSs (Linux).
|
-/local_path
+ | /local_path
|
-Mount point, that is, the directory created on the ECS for mounting the file system. Set this parameter to the local path in the mount command that is used in Mounting an NFS File System to ECSs (Linux).
+ | Mount point, that is, the directory created on the ECS for mounting the file system. Set this parameter to the local path in the mount command that is used in Mounting an NFS File System to ECSs (Linux).
|
-nfs
+ | nfs
|
-Mount type, that is, file system or partition type. Set it to nfs.
+ | Mount type, that is, file system or partition type. Set it to nfs.
|
-vers=3,timeo=600,nolock
+ | vers=3,timeo=600,nolock
|
-Mount options, used to set mount parameters. Use commas (,) to separate between multiple options.
+ | Mount options, used to set mount parameters. Use commas (,) to separate between multiple options.
- vers: file system version. The value 3 indicates NFSv3.
- timeo: waiting time before the NFS client retransmits a request. The unit is 0.1 second. The recommended value is 600.
- nolock: specifies whether to lock files on the server using the NLM protocol.
|
@@ -65,15 +65,14 @@
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 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 script
For 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 Turbo file systems: mount -o nolock -o casesensitive=yes IP address:/! 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",0
@@ -87,3 +86,10 @@ ws.Run "C:\test\auto_mount.bat /start",0
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0026.html b/docs/sfs/umn/sfs_01_0026.html
index 18175f78..fdf06abd 100644
--- a/docs/sfs/umn/sfs_01_0026.html
+++ b/docs/sfs/umn/sfs_01_0026.html
@@ -12,7 +12,7 @@
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
+ - 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.
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.
-Figure 1 Checking software repositories
+Figure 1 Checking software repositories
- 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. Figure 3 Checking whether the software repository has been enabled
+ If status is enabled, as shown in Figure 3, the software repository has been enabled. Figure 3 Checking whether 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.
-Figure 4 Checking software repositories
- - 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
+ 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.
+Figure 4 Checking software repositories
+ - 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
- - 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. Figure 7 Checking whether the software repository has been enabled
+ - Run the following command to update and add software repositories.
zypper refresh
+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. Figure 7 Checking whether the software repository has been enabled
Ubuntu- Run the following command to add a software repository.
apt-add-repository http://archive.canonical.com/ubuntuFigure 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
+ - Run the following command to update and add software repositories.
apt-get update
+Figure 9 Updating and adding repositories
@@ -37,3 +37,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0030.html b/docs/sfs/umn/sfs_01_0030.html
index 37e480b0..52d6c474 100644
--- a/docs/sfs/umn/sfs_01_0030.html
+++ b/docs/sfs/umn/sfs_01_0030.html
@@ -22,7 +22,7 @@
- Monitoring
- - Auditing
+ - Auditing
diff --git a/docs/sfs/umn/sfs_01_0032.html b/docs/sfs/umn/sfs_01_0032.html
index 9561fb5b..e7a36903 100644
--- a/docs/sfs/umn/sfs_01_0032.html
+++ b/docs/sfs/umn/sfs_01_0032.html
@@ -7,13 +7,13 @@
This section describes the procedure for granting permissions (see Figure 1).
PrerequisitesLearn about the permissions (see Permissions) supported by SFS and choose policies or roles according to your requirements.
Restrictions- All system-defined policies and custom policies are supported in SFS Turbo file systems.
+ Restrictions- Both system-defined policies and custom policies are supported in SFS Turbo file systems.
- Process FlowFigure 1 Process for granting SFS permissions
- - 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.
+Process FlowFigure 1 Process for granting SFS permissions
+ - 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 SFS Console using the created user, and verify that the user only has read permissions for SFS.
-- Choose Scalable File Service. Click Create File System on SFS Console. If a message appears indicating that you have insufficient permissions to perform the operation, the SFS Turbo ReadOnlyAccess policy has already taken effect.
- Choose any other service. If a message appears indicating that you have insufficient permissions to access the service, the SFS Turbo ReadOnlyAccess policy has already taken effect.
+ - 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.
+- Choose Scalable File Service. Click Create File System on the SFS console. If a message appears indicating that you have insufficient permissions to perform the operation, the SFS Turbo ReadOnlyAccess policy has already taken effect.
- Choose any other service. If a message appears indicating that you have insufficient permissions to access the service, the SFS Turbo ReadOnlyAccess policy has already taken effect.
diff --git a/docs/sfs/umn/sfs_01_0033.html b/docs/sfs/umn/sfs_01_0033.html
index 37ae4fa1..77f3a54f 100644
--- a/docs/sfs/umn/sfs_01_0033.html
+++ b/docs/sfs/umn/sfs_01_0033.html
@@ -1,7 +1,7 @@
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.
@@ -17,7 +17,7 @@
]
}
- Example 2: Denying file system deletion
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
-The following method can be used if you need to assign permissions of the SFS Turbo FullAccess policy to a user but also forbid the user from deleting file systems. Create a custom policy for denying file system deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on SFS except deleting file systems. The following is an example of a deny policy:
+The following method can be used if you need to assign permissions of the SFS Turbo FullAccess policy to a user but also forbid the user from deleting file systems. Create a custom policy for denying file system deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on SFS except deleting file systems. The following is an example of a deny policy:
{
"Version": "1.1",
"Statement": [
diff --git a/docs/sfs/umn/sfs_01_0034.html b/docs/sfs/umn/sfs_01_0034.html
index 2304936f..f1ce263b 100644
--- a/docs/sfs/umn/sfs_01_0034.html
+++ b/docs/sfs/umn/sfs_01_0034.html
@@ -4,9 +4,9 @@
diff --git a/docs/sfs/umn/sfs_01_0036.html b/docs/sfs/umn/sfs_01_0036.html
index 795c5c22..9c5d3703 100644
--- a/docs/sfs/umn/sfs_01_0036.html
+++ b/docs/sfs/umn/sfs_01_0036.html
@@ -4,13 +4,13 @@
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.
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.
- ScenariosMulti-VPC access can be configured for an SFS Capacity-Oriented 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.
- This section describes how to configure multi-VPC access for an SFS Capacity-Oriented file system.
+ ScenariosMulti-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.
- 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 address/address segment 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.
+ 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.
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.
-Figure 1 Adding VPCs
+Figure 1 Adding VPCs
- 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.
Table 1 Parameter descriptionParameter
|
@@ -36,7 +36,7 @@
|---|
- 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.Figure 2 Adding an authorized address or segment
+ - 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.Figure 2 Adding an authorized address or segment
Table 2 Parameter descriptionParameter
|
@@ -79,6 +79,102 @@
+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 descriptionParameter
+ |
+Description
+ |
+
|---|
+
+VPC
+ |
+VPC you want to add, for example, vpc-30e0. If no VPC is available, create one.
+ |
+
+Authorizations
+ |
+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
+ - Set the parameters as prompted.
+ Table 4 Parameters for purchasing an endpointParameter
+ |
+Description
+ |
+
|---|
+
+Region
+ |
+Region where the VPC endpoint is located. Ensure that this region is the same as the one where the planned general purpose file system resides.
+ |
+
+Service Category
+ |
+Select Find a service by name.
+After entering the service name, click Verify.
+If Service name found is displayed, proceed with subsequent steps.
+If Service name not found is displayed, check whether the entered service name is correct. If the problem persists, contact the website administrator.
+ |
+
+VPC
+ |
+Select the VPC you have added as authorized VPC of the general purpose file system.
+ |
+
+Tag
+ |
+Optional
+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.
+
+ |
+
+
+
+ Table 5 describes the tag parameters.
+ Table 5 Tag parameter descriptionParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Tag key
+ |
+Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS.
+A tag key:
+- Can contain 1 to 36 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
+ |
+Key_0001
+ |
+
+Tag value
+ |
+A tag value can be repetitive or left blank.
+A tag value:
+- Can contain 0 to 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
+ |
+Value_0001
+ |
+
+
+
+
+
+ - Click Next.
- If you do not need to modify the specifications, click Submit.
- If you need to modify the specifications, click Previous, modify the parameters as needed, and then click Submit.
+ - Go back to the VPC endpoint list and check whether the status of the VPC endpoint changes to Accepted. If so, the VPC endpoint has been connected to the VPC endpoint service.
+ VerificationAfter another VPC is configured for the file system, if the file system can be mounted to ECSs in the VPC and the ECSs can access the file system, the configuration is successful.
ExampleA user creates an SFS Capacity-Oriented file system A in VPC-B. The network segment is 10.0.0.0/16. The user has an ECS D in VPC-C, using the private IP address 192.168.10.11 in network segment 192.168.10.0/24. If the user wants to mount file system A to ECS D and allow the file system to be read and written, the user needs to add VPC-C to file system A's VPC list, add ECS D's private IP address or address segment to the authorized addresses of VPC-C, and then set Read-Write Permission to Read-write.
@@ -91,3 +187,10 @@
ScenariosBy 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.
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.
Figure 1 Configuring DNS
+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.
Figure 1 Configuring DNS
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
@@ -17,14 +17,14 @@
- Run the following command to check whether the editing is successful:
lsattr /etc/resolv.conf
If the information shown in Figure 2 is displayed, the file is locked.
-Figure 2 A locked file
+Figure 2 A locked file
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.
Figure 3 Page for network and sharing center
- - In the Activity area, select Properties. See Figure 4.
Figure 4 Local area connection
- - In the Local Area Connection Properties dialog box that is displayed, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. See Figure 5.
Figure 5 Local area connection properties
- - 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.
Figure 6 Configuring DNS on Windows
+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.
Figure 3 Page for network and sharing center
+ - In the Activity area, select Properties. See Figure 4.
Figure 4 Local area connection
+ - In the Local Area Connection Properties dialog box that is displayed, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. See Figure 5.
Figure 5 Local area connection properties
+ - 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.
Figure 6 Configuring DNS on Windows
File System Resizing
ScenariosYou can expand or shrink the capacity of a file system when needed.
- Limitations and ConstraintsThe capacity of an SFS Turbo file system can be expanded but cannot be reduced.
- SFS Capacity-Oriented file systems support resizing, which does not affect services.
- 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 latency. You are advised to expand capacity during off-peak hours.
+ ConstraintsSFS 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.
- Rules for ResizingThe rules for resizing an SFS Capacity-Oriented file system are as follows:
+ PrecautionsThe rules for resizing an SFS Capacity-Oriented file system are as follows:
- Expanding a file system
Total capacity of a file system after expansion ≤ (Capacity quota of the cloud account - Total capacity of all the other file systems owned by the cloud account)
-For example, cloud account A has a quota of 500 TB. This account has already created three file systems: SFS1 (350 TB), SFS2 (50 TB), and SFS3 (70 TB). If this account needs to expand SFS2, the new capacity of SFS2 cannot be greater than 80 TB. Otherwise, the system will display a message indicating an insufficient quota and the expansion operation will fail.
- - Shrinking a file system
- When a shrink error or failure occurs on a file system, it takes approximately five minutes for the file system to restore to the available state.
- After a shrink operation fails, you can try shrinking the file system capacity again, but you cannot expand it.
- Total capacity of a file system after shrinking ≥ Used capacity of the file system
For example, cloud account B has created a file system, SFS1. The total capacity and used capacity of SFS1 are 50 TB and 10 TB respectively. When shrinking SFS1, the user cannot set a new capacity smaller than 10 TB.
+For example, a cloud account has a quota of 500 TB. This account has already created three file systems: SFS1 (350 TB), SFS2 (50 TB), and SFS3 (70 TB). If this account needs to expand SFS2, the new capacity of SFS2 cannot be greater than 80 TB. Otherwise, the system will display a message indicating an insufficient quota and the expansion operation will fail.
+ - Shrinking a file system
- When a shrink error or failure occurs on a file system, it takes approximately five minutes for the file system to restore to the available state.
- After a shrink operation fails, you can only reattempt to shrink the file system storage capacity but cannot expand it directly.
- Total capacity of a file system after shrinking ≥ Used capacity of the file system
For example, a cloud account has created a file system, SFS1. The total capacity and used capacity of SFS1 are 50 TB and 10 TB respectively. When shrinking SFS1, the user cannot set a new capacity smaller than 10 TB.
- 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, as shown in Figure 1.
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.
+ 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
+ - Enter a new capacity and click OK. The following tables describe the parameters.
Table 1 SFS Capacity-Oriented file system resizing parametersParameter
|
Description
@@ -58,7 +59,7 @@
|
|---|
New Capacity
|
New storage capacity of the file system
-Value constraints: - For a Standard, Standard – Enhanced, Performance, or Performance – Enhanced file system, the expansion increment is 100 GB. A Standard or Performance file system can be expanded to up to 32 TB. 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. The maximum capacity that can be set cannot exceed 1 PB.
+ Value constraints: - For a Standard, Standard – Enhanced, Performance, or Performance – Enhanced file system, the 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.
|
@@ -74,3 +75,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0040.html b/docs/sfs/umn/sfs_01_0040.html
index 22bf1d05..08756d60 100644
--- a/docs/sfs/umn/sfs_01_0040.html
+++ b/docs/sfs/umn/sfs_01_0040.html
@@ -1,16 +1,16 @@
Quotas
-What Is Quota?Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.
+ What Is Quota?Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.
If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.
- How Do I View My Quotas?- Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - In the upper right corner of the page, click
 .The Service Quota page is displayed.
+How Do I View My Quotas?- Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - In the upper right corner of the page, click
 .The Quotas page is displayed.
- View the used and total quota of each type of resources on the displayed page.
If a quota cannot meet service requirements, apply for a higher quota.
How Do I Apply for a Higher Quota?The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
- - Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- Quota information, which includes:
- Service name
- Quota type
- Required quota
Learn how to obtain the service hotline and email address.
diff --git a/docs/sfs/umn/sfs_01_0042.html b/docs/sfs/umn/sfs_01_0042.html
index b0382c9e..18b5a311 100644
--- a/docs/sfs/umn/sfs_01_0042.html
+++ b/docs/sfs/umn/sfs_01_0042.html
@@ -2,12 +2,12 @@
Encryption
Creating an Encrypted File SystemTo 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.
- For SFS Turbo file systems, no authorization is required.
- You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system.
+ 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.
For details about how to create an encrypted file system, see Create a File System.
- Unmounting an Encrypted File SystemIf the CMK used by the encrypted file system is disabled or planned to be deleted, 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 the file system, see Unmount a File System.
+ Unmounting an Encrypted File SystemIf 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
diff --git a/docs/sfs/umn/sfs_01_0043.html b/docs/sfs/umn/sfs_01_0043.html
index 9a9c2348..7018f5db 100644
--- a/docs/sfs/umn/sfs_01_0043.html
+++ b/docs/sfs/umn/sfs_01_0043.html
@@ -1,12 +1,12 @@
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 4.2 Creating 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 section 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 can only contain letters, digits, hyphens (-), and underscores (_).
- A tag value can contain a maximum of 43 characters and can be an empty string. It can only contain letters, digits, hyphens (-), and underscores (_).
- - You can add a maximum of 20 tags to one file system.
- The tag keys of the same file system must be unique.
- Once created, the tag keys of the file system cannot be edited. You can only edit the tag values. You can delete tags.
- Procedure- 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.
Figure 1 Managing file system tags
- - Click the Tags tab.
- On the Tags tab page, click Add Tag. The Add 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.
+- 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.
Figure 1 Managing file system tags
+ - 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.
Return to the tag list, and you can see the tags you have just added. You can edit and delete the added tags.
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0044.html b/docs/sfs/umn/sfs_01_0044.html
index 9b14ece6..ff8e0484 100644
--- a/docs/sfs/umn/sfs_01_0044.html
+++ b/docs/sfs/umn/sfs_01_0044.html
@@ -1,18 +1,20 @@
Backup
- Only SFS Turbo file systems can be backed up using CBR while SFS Capacity-Oriented file systems cannot.
+ You can only back up SFS Turbo file systems using CBR while you cannot back up SFS Capacity-Oriented and general purpose file systems.
ScenariosA 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.
Creating a File System BackupEnsure that the target file system is available. Or, the backup task cannot start. This procedure describes how to manually create a file system backup.
- - Log in to CBR Console.
- In the navigation pane on the left, choose SFS Turbo Backups.
- Create a backup vault by following the instructions in section "Creating an SFS Turbo Backup Vault" in the Cloud Backup and Recovery User Guide. Then, create a backup by following the instructions in section "Creating an SFS Turbo Backup."
- The system automatically backs up the file system.
You can view the backup creation status on the Backups tab page. When the Status of the backup changes to Available, the backup has been created.
+ 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.
+
+- Log in to CBR Console.
- In the navigation pane on the left, choose SFS Turbo Backups.
- Create a backup vault by referring to section "Creating an SFS Turbo Backup Vault" and then create a backup by referring to section "Creating an SFS Turbo Backup" in the Cloud Backup and Recovery User Guide.
- The system automatically backs up the file system.
You can view the backup creation status on the Backups tab page. When the Status of the backup changes to Available, the backup has been created.
- If the file system becomes faulty or an error occurred, you can restore the backup data to a new file system. For details, see Using a Backup to Create a File System.
Using a Backup to Create a File SystemIn 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 New File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1.
Figure 1 Create File System
-
+ - 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.
Figure 1 Create File System
+ - For detailed parameter descriptions, see table "Parameter description" under Table 3.
- 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.
@@ -24,3 +26,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0047.html b/docs/sfs/umn/sfs_01_0047.html
index c99f12a9..581df451 100644
--- a/docs/sfs/umn/sfs_01_0047.html
+++ b/docs/sfs/umn/sfs_01_0047.html
@@ -1,121 +1,122 @@
SFS Metrics
-FunctionThis 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.
+ General purpose file systems do not support monitoring. The monitoring metrics described in this section apply only to SFS Capacity-Oriented file systems.
+ FunctionThis 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.
Metrics
- Table 1 SFS metricsMetric ID
+Table 1 SFS metricsMetric ID
|
-Metric Name
+ | Metric Name
|
-Description
+ | Description
|
-Value Range
+ | Value Range
|
-Monitored Object
+ | Monitored Object
|
-Monitoring Period (Raw Data)
+ | Monitoring Period (Raw Data)
|
|---|
-read_bandwidth
+ | read_bandwidth
|
-Read Bandwidth
+ | Read Bandwidth
|
-Read bandwidth of a file system within a monitoring period
+ | Read bandwidth of a file system within a monitoring period
Unit: byte/s
|
-≥ 0 bytes/s
+ | ≥ 0 bytes/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
-write_bandwidth
+ | write_bandwidth
|
-Write Bandwidth
+ | Write Bandwidth
|
-Write bandwidth of a file system within a monitoring period
+ | Write bandwidth of a file system within a monitoring period
Unit: byte/s
|
-≥ 0 bytes/s
+ | ≥ 0 bytes/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 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
+ | Read and write bandwidth of a file system within a monitoring period
Unit: byte/s
|
-≥ 0 bytes/s
+ | ≥ 0 bytes/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
-read_ops
+ | read_ops
|
-Read OPS
+ | Read OPS
|
-Read operations of a file system within a monitoring period
+ | Read operations of a file system within a monitoring period
Unit: count/s
|
-≥ 0 counts/s
+ | ≥ 0 counts/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
-write_ops
+ | write_ops
|
-Write OPS
+ | Write OPS
|
-Write operations of a file system within a monitoring period
+ | Write operations of a file system within a monitoring period
Unit: count/s
|
-≥ 0 counts/s
+ | ≥ 0 counts/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
-rw_ops
+ | rw_ops
|
-Read Write OPS
+ | Read Write OPS
|
-Read and write operations of a file system within a monitoring period
+ | Read and write operations of a file system within a monitoring period
Unit: count/s
|
-≥ 0 counts/s
+ | ≥ 0 counts/s
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
-used_capicity
+ | used_capicity
|
-Used Capacity
+ | Used Capacity
|
-Used capacity of a file system within a monitoring period
+ | Used capacity of a file system within a monitoring period
Unit: byte
|
-≥ 0 bytes
+ | ≥ 0 bytes
|
-SFS file system
+ | SFS file system
|
-4 minutes
+ | 4 minutes
|
@@ -123,24 +124,23 @@
Dimension
- Key
+Key
|
-Value
+ | Value
|
|---|
-share_id
+ | share_id
|
-SFS file system
+ | SFS file system
|
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. In the file system list, click View Metric in the Operation column of the target 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.
-Figure 1 Monitoring graphs
+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.
+Figure 1 Monitoring graphs
| 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
|
@@ -121,7 +124,7 @@
Capacity Usage
|
Percentage of used capacity in the total capacity
-Unit: Percent
+Unit: percent
|
0% to 100%
|
@@ -150,7 +153,7 @@
|---|
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 target file system.
+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 target 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.
Auditing
+Supported SFS Operations
ScenariosCloud Trace Service (CTS) records operations of SFS resources, facilitating query, audit, and backtracking.
+ 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.
PrerequisitesYou 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 operations traced by CTSOperation
+Table 1 SFS Capacity-Oriented operations traced by CTSOperation
|
Resource Type
|
@@ -94,18 +95,25 @@
|---|
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 TrackerThis 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 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 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.
Prerequisites- A VPC has been created.
- ECSs that function as head nodes and compute nodes have been created, and have been assigned to the VPC.
- SFS has been enabled.
- Example Configuration- Log in to 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 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 7143ed83..93a2c7e5 100644
--- a/docs/sfs/umn/sfs_01_0053.html
+++ b/docs/sfs/umn/sfs_01_0053.html
@@ -10,7 +10,7 @@
Prerequisites- A VPC has been created.
- ECSs that function as upload workstations and editing workstations have been created, and have been assigned to the VPC.
- SFS has been enabled.
Example Configuration- Log in to 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.
ContextFor 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:
- 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 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 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.
- Example Configuration- Log in to 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 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.
diff --git a/docs/sfs/umn/sfs_01_0055.html b/docs/sfs/umn/sfs_01_0055.html
index 265a281d..de0e8944 100644
--- a/docs/sfs/umn/sfs_01_0055.html
+++ b/docs/sfs/umn/sfs_01_0055.html
@@ -4,11 +4,11 @@
ContextSFS 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.
- Configuration Process- Log in to 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 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.
- Example Configuration- Log in to 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.
diff --git a/docs/sfs/umn/sfs_01_0057.html b/docs/sfs/umn/sfs_01_0057.html
index aee59c2b..913ef50f 100644
--- a/docs/sfs/umn/sfs_01_0057.html
+++ b/docs/sfs/umn/sfs_01_0057.html
@@ -13,7 +13,7 @@
- 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.
-
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0060.html b/docs/sfs/umn/sfs_01_0060.html
index 935e50b6..0ffcd490 100644
--- a/docs/sfs/umn/sfs_01_0060.html
+++ b/docs/sfs/umn/sfs_01_0060.html
@@ -1,14 +1,14 @@
Data Fails to Be Written into a File System Mounted to ECSs Running Different Types of Operating Systems
- SymptomIf a file system is mounted to a Linux ECS and a Windows ECS, you cannot write data to the files created by the Linux ECS on the Windows ECS.
+ SymptomIf 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.
Possible CausesA shared NFS file system belongs to the root user and cannot be modified. The write permission is granted to a user only when both the values of UID and GID of the user are 0. You can check your UID using Windows commands. If the value of UID is, for example, -2, you do not have the write permission.
Fault DiagnosisTo address this problem, modify the registry and change both UID and GID values to 0 for NFS accesses from Windows.
- 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.
Figure 1 Entering 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.
Figure 2 Adding values
+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.
Figure 1 Entering 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.
Figure 2 Adding values
- After modifying the registry, restart the server for the modification to take effect.
@@ -18,3 +18,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0061.html b/docs/sfs/umn/sfs_01_0061.html
index 8d6f8c8f..a7866bc3 100644
--- a/docs/sfs/umn/sfs_01_0061.html
+++ b/docs/sfs/umn/sfs_01_0061.html
@@ -7,8 +7,8 @@
Fault DiagnosisTake 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.XXXXXXXXX.com\share-396876e8, as shown in Figure 2. Figure 1 Mount point
- Figure 2 Physical path
+ 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. Figure 1 Mount point
+ Figure 2 Physical path
@@ -19,3 +19,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0062.html b/docs/sfs/umn/sfs_01_0062.html
index dffb2643..b80af2fa 100644
--- a/docs/sfs/umn/sfs_01_0062.html
+++ b/docs/sfs/umn/sfs_01_0062.html
@@ -8,10 +8,10 @@
Fault DiagnosisInstall 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. example.com:/share-xxx on /local_path type nfs (rw,vers=3,timeo=600,nolock,addr=)
@@ -25,3 +25,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0063.html b/docs/sfs/umn/sfs_01_0063.html
index 96a50427..fb359745 100644
--- a/docs/sfs/umn/sfs_01_0063.html
+++ b/docs/sfs/umn/sfs_01_0063.html
@@ -9,14 +9,14 @@
Solution 2: Modify the registry to allow guest access (suitable for versions later than Windows Server 2016).
SolutionSolution 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 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
- 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
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 the 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 SFS Turbo file system types, see File System Types.
diff --git a/docs/sfs/umn/sfs_01_0071.html b/docs/sfs/umn/sfs_01_0071.html
index acdf40e8..7e59f0db 100644
--- a/docs/sfs/umn/sfs_01_0071.html
+++ b/docs/sfs/umn/sfs_01_0071.html
@@ -3,6 +3,7 @@
What Is the Maximum Size of a File That Can Be Stored in a File System?
For SFS Capacity-Oriented file systems, the maximum supported size of a file is 240 TB.
For SFS Turbo file systems, the maximum supported size of a file is 16 TB.
+ For general purpose file systems, the maximum supported size of a file is 240 TB.
diff --git a/docs/sfs/umn/sfs_01_0073.html b/docs/sfs/umn/sfs_01_0073.html
index 2943e9a2..08059c56 100644
--- a/docs/sfs/umn/sfs_01_0073.html
+++ b/docs/sfs/umn/sfs_01_0073.html
@@ -2,6 +2,7 @@
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.
- 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 d74ee2f5..d52d381b 100644
--- a/docs/sfs/umn/sfs_01_0074.html
+++ b/docs/sfs/umn/sfs_01_0074.html
@@ -2,7 +2,8 @@
How Many Servers Can a File System Be Mounted 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 500 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_0076.html b/docs/sfs/umn/sfs_01_0076.html
index 6eeb3b4c..1fb5e7c6 100644
--- a/docs/sfs/umn/sfs_01_0076.html
+++ b/docs/sfs/umn/sfs_01_0076.html
@@ -2,6 +2,7 @@
Can the Capacity of a File System Be Expanded?
Both SFS Capacity-Oriented and SFS Turbo file systems can be expanded by capacity resizing.
+ General purpose file systems have no capacity limit and do not support resizing.
diff --git a/docs/sfs/umn/sfs_01_0079.html b/docs/sfs/umn/sfs_01_0079.html
index 8f5559ef..9ab0870b 100644
--- a/docs/sfs/umn/sfs_01_0079.html
+++ b/docs/sfs/umn/sfs_01_0079.html
@@ -1,11 +1,7 @@
-
- Networks
-
-
-
+ Networks
+
- Can a File System Be Accessed Across VPCs?
diff --git a/docs/sfs/umn/sfs_01_0080.html b/docs/sfs/umn/sfs_01_0080.html
index bb09aa2c..99a54353 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 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 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.
diff --git a/docs/sfs/umn/sfs_01_0081.html b/docs/sfs/umn/sfs_01_0081.html
index 45c53453..64876492 100644
--- a/docs/sfs/umn/sfs_01_0081.html
+++ b/docs/sfs/umn/sfs_01_0081.html
@@ -2,8 +2,8 @@
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.
- After an SFS Turbo file system is created, the system automatically enables the security group port required by the NFS protocol in the SFS Turbo file system. This ensures that the SFS Turbo file system can be accessed by your server 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, choose Access Control > Security Groups of the VPC console and locate the target security group.
- You are advised to use an independent security group for an SFS Turbo instance to isolate it from service nodes.
+ 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.
Example Value- Inbound rule
Direction
@@ -26,7 +26,7 @@
| IP Address
|
-0.0.0.0/0 (configurable)
+ | 0.0.0.0/0 (All IP addresses are allowed. It can be modified.)
|
One port corresponds to one access rule. You need to add information to the ports one by one.
|
@@ -55,7 +55,7 @@
IP Address
|
-0.0.0.0/0 (configurable)
+ | 0.0.0.0/0 (All IP addresses are allowed. It can be modified.)
|
One port corresponds to one access rule. You need to add information to the ports one by one.
|
@@ -63,8 +63,11 @@
|---|
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.
+ 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 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.
diff --git a/docs/sfs/umn/sfs_01_0091.html b/docs/sfs/umn/sfs_01_0091.html
index 08badc1a..3fec0dde 100644
--- a/docs/sfs/umn/sfs_01_0091.html
+++ b/docs/sfs/umn/sfs_01_0091.html
@@ -10,9 +10,9 @@
- What Resources Does SFS Occupy?
- - How Is the SFS Turbo Capacity Quota Calculated?
+ - Why Is the Capacity Displayed as 250TB After I Mount My General Purpose File System?
- - How Do I Make the Most Out of My SFS Turbo File System?
+ - How Is the SFS Turbo Capacity Quota Calculated?
diff --git a/docs/sfs/umn/sfs_01_0094.html b/docs/sfs/umn/sfs_01_0094.html
index f4094d8b..6ec3d100 100644
--- a/docs/sfs/umn/sfs_01_0094.html
+++ b/docs/sfs/umn/sfs_01_0094.html
@@ -2,7 +2,7 @@
What Resources Does SFS Occupy?
To ensure that file systems can be used properly, the service occupies the following resources:
-
|
|---|
-Mount point
+ | Mount Point
|
NOTE: x is a digit or letter.
@@ -44,3 +44,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0104.html b/docs/sfs/umn/sfs_01_0104.html
index c6e4faa1..87d13a4c 100644
--- a/docs/sfs/umn/sfs_01_0104.html
+++ b/docs/sfs/umn/sfs_01_0104.html
@@ -8,28 +8,34 @@
|
-2024-07-30
+ | 2024-10-23
|
-Updated the following content:
-
+ | Updated the following content:
+- Added descriptions about General Purpose File System.
- Deleted section "Supported OSs."
|
-2023-08-29
+ | 2024-07-30
+ |
+Updated the following content:
+
+ |
+
+2023-08-29
|
Updated the following content:
Added a description about how to reach 100,000 IOPS in a test with an SFS Turbo Performance Enhanced file system.
|
-2023-07-03
+ | 2023-07-03
|
Updated the following content:
-Added the description about the maximum number of tags that can be added to a file system.
+Added a description about the maximum number of tags that can be added to a file system.
|
2023-02-20
|
Updated the following content:
-Added section "Permissions."
+Added descriptions about permissions management.
|
2023-02-10
diff --git a/docs/sfs/umn/sfs_01_0107.html b/docs/sfs/umn/sfs_01_0107.html
index 9c138d76..5923e672 100644
--- a/docs/sfs/umn/sfs_01_0107.html
+++ b/docs/sfs/umn/sfs_01_0107.html
@@ -4,7 +4,9 @@
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
- - Run the following commands on the Linux ECS to install the rclone tool:
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-*
- - Run the following command to synchronize data:
rclone copy /mnt/src /mnt/dst -P --transfers 32 --checkers 64
- Set transfers and checkers based on the system specifications. The parameters are described as follows:
- - transfers: number of files that can be transferred concurrently
- checkers: number of files that can be scanned concurrently
- P: data copy progress
+ - 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.
diff --git a/docs/sfs/umn/sfs_01_0118.html b/docs/sfs/umn/sfs_01_0118.html
index f8b621b9..7e380c90 100644
--- a/docs/sfs/umn/sfs_01_0118.html
+++ b/docs/sfs/umn/sfs_01_0118.html
@@ -1,31 +1,31 @@
Failed to Create an SFS Turbo File System
- SymptomAn SFS Turbo file system fails to be created.
+ SymptomAn SFS Turbo file system fails to be created.
- Fault DiagnosisThe following fault causes are sequenced based on their occurrence probability.
- If the fault persists after you have ruled out a cause, check other causes.
- Figure 1 Fault diagnosis
+ Fault DiagnosisThe following fault causes are sequenced based on their occurrence probability.
+ If the fault persists after you have ruled out one cause, move on to the next one in the list.
+ Figure 1 Fault diagnosis
- Table 1 Fault diagnosisPossible Cause
+Table 1 Fault diagnosisPossible Cause
|
-Solution
+ | Solution
|
|---|
-The quota is insufficient.
+ | 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. to increase the quota.
|
-The subnet does not have sufficient IP addresses.
+ | The subnet does not have sufficient IP addresses.
|
-If the subnet IP addresses are insufficient, you can change the subnet or release other IP addresses in the subnet.
+ | If the IP addresses in the subnet are insufficient, change the subnet or release IP addresses in the subnet.
|
-The background capacity is insufficient.
+ | The background resources are insufficient.
|
- to expand the capacity.
+ | Background resources, such as compute and storage resources, have reached the upper limit. for technical consultation.
|
@@ -39,3 +39,10 @@
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0119.html b/docs/sfs/umn/sfs_01_0119.html
index aff7ae8c..5d44ff7a 100644
--- a/docs/sfs/umn/sfs_01_0119.html
+++ b/docs/sfs/umn/sfs_01_0119.html
@@ -5,7 +5,7 @@
Possible CausesAutomatic mounting is not configured. The server is automatically disconnected from the file system after restart.
SolutionConfigure automatic mounting for the server so that the file system will be automatically mounted to the server after startup. For details, see .
+
diff --git a/docs/sfs/umn/sfs_01_0120.html b/docs/sfs/umn/sfs_01_0120.html
index ce72969b..7f2f4044 100644
--- a/docs/sfs/umn/sfs_01_0120.html
+++ b/docs/sfs/umn/sfs_01_0120.html
@@ -4,7 +4,7 @@
Before you start, understand the following concepts.
NFSNetwork File System (NFS) is a distributed file system protocol that allows different computers and operating systems to share data over a network.
- File SystemA file system provides users with shared file storage service through NFS. It is used for accessing network files remotely. After a user creates a mount point on the management console, the file system can be mounted to multiple servers and is accessible through the standard POSIX.
+ File SystemA 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.
POSIXPortable 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.
diff --git a/docs/sfs/umn/sfs_01_0125.html b/docs/sfs/umn/sfs_01_0125.html
index 4ee4cc10..3ebdc427 100644
--- a/docs/sfs/umn/sfs_01_0125.html
+++ b/docs/sfs/umn/sfs_01_0125.html
@@ -7,10 +7,10 @@
Fault DiagnosisCheck 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.
- - 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 in the SFS Turbo file system. This ensures that the SFS Turbo file system can be accessed by your server 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, choose Access Control > Security Groups of the VPC console and locate the target security group.
-You are advised to use an independent security group for an SFS Turbo instance 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.
+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.
- Click OK. Access the file system again for verification.
diff --git a/docs/sfs/umn/sfs_01_0134.html b/docs/sfs/umn/sfs_01_0134.html
new file mode 100644
index 00000000..503cdfa4
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0134.html
@@ -0,0 +1,100 @@
+
+
+ Configure a VPC Endpoint
+ ContextVPC Endpoint provides reliable channels to connect VPCs to general purpose file systems. By configuring VPC endpoints, compute resources in VPCs can access general purpose file systems.
+ 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.
+ - 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
+ - Set the parameters as prompted.
+ Table 1 Parameters for purchasing an endpointParameter
+ |
+Description
+ |
+
|---|
+
+Region
+ |
+Region where the VPC endpoint is located. Ensure that this region is the same as the one where the planned general purpose file system resides.
+ |
+
+Service Category
+ |
+Select Find a service by name.
+Enter com.t-systems.otc.eu-de.lz02.obsv2.ipv4.
+After entering the service name, click Verify.
+If Service name found is displayed, proceed with subsequent steps.
+If Service name not found is displayed, check whether the entered service name is correct. If the problem persists, contact the website administrator.
+ |
+
+VPC
+ |
+VPC where the planned general purpose file system and ECSs reside.
+ |
+
+Tag
+ |
+Optional
+VPC endpoint tags. Each tag consists of a key and a value.
+Tag keys and values must meet the requirements listed in Table 2.
+ 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.
+
+ |
+
+
+
+ Table 2 describes the tag parameters.
+ Table 2 Tag parameter descriptionParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Tag key
+ |
+Each tag has a unique key. You can customize the key or select the key of an existing tag created in TMS.
+A tag key:
+- Can contain 1 to 36 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
+ |
+Key_0001
+ |
+
+Tag value
+ |
+A tag value can be repetitive or left blank.
+A tag value:
+- Can contain 0 to 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
+ |
+Value_0001
+ |
+
+
+
+
+
+ - Click Next.
- If you do not need to modify the specifications, click Submit.
- If you need to modify the specifications, click Previous, modify the parameters as needed, and then click Submit.
+ - Go back to the VPC endpoint list and check whether the status of the VPC endpoint changes to Accepted. If so, the VPC endpoint has been connected to the VPC endpoint service.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0139.html b/docs/sfs/umn/sfs_01_0139.html
new file mode 100644
index 00000000..f6edf3c3
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0139.html
@@ -0,0 +1,11 @@
+
+
+ Why Is the Capacity Displayed as 250TB After I Mount My General Purpose File System?
+ There is no limit on the capacity of a general purpose file system. When you run the df -h command on the client, the system returns 250TB for display purposes. This value is meaningless, and the available capacity is not limited.
+
+
+
diff --git a/docs/sfs/umn/sfs_01_0340.html b/docs/sfs/umn/sfs_01_0340.html
new file mode 100644
index 00000000..fc5f075f
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0340.html
@@ -0,0 +1,19 @@
+
+
+
+ Auditing
+
+
+
+
+
diff --git a/docs/sfs/umn/sfs_01_0346.html b/docs/sfs/umn/sfs_01_0346.html
new file mode 100644
index 00000000..21b27afe
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0346.html
@@ -0,0 +1,91 @@
+
+
+ Viewing a File System
+ You can search for file systems by file system name keyword and view their basic information.
+ Procedure- Log in to the SFS console.
- In the file system list, view the file systems you have created. Table 1 describes the file system parameters.
+ Table 1 Parameter descriptionParameter
+ |
+Description
+ |
+
|---|
+
+Name
+ |
+Name of the file system, for example, sfs-name-001
+ |
+
+Data Redundancy Policy
+ |
+Only Multi-AZ is supported currently.
+ |
+
+AZ
+ |
+Availability zone where the file system is located
+ |
+
+Status
+ |
+Possible values are Available, Unavailable, Frozen, Creating, Deleting, Deletion error, Creation failed, Expanding, Expansion error, Capacity reducing, Capacity reduction error, and Capacity reduction failed.
+ |
+
+Protocol Type
+ |
+File system protocol, which is NFS
+ |
+
+Used Capacity (GB)
+ |
+File system space already used for data storage
+ NOTE: This information is refreshed every 15 minutes.
+
+ |
+
+Maximum Capacity (GB)
+ |
+Maximum capacity of the file system
+ |
+
+Encrypted
+ |
+Encryption status of the file system. The value can be Yes or No.
+ |
+
+Mount Point
+ |
+File system mount point, which is in the format of File system domain name:/Path or File system IP address:/
+ NOTE: If the mount point is too long to display completely, adjust the column width.
+
+ |
+
+Operation
+ |
+For an SFS Capacity-Oriented file system, operations include resizing, deletion, and monitoring metric viewing.
+For an SFS Turbo file system, operations include capacity expansion, deletion, and monitoring metric viewing.
+For a general purpose file system, operations include deletion only.
+ |
+
+
+
+ - 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
+ - (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.
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_0347.html b/docs/sfs/umn/sfs_01_0347.html
new file mode 100644
index 00000000..a3b7cdcc
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_0347.html
@@ -0,0 +1,29 @@
+
+
+ Deleting a File System
+ Data in a deleted file system cannot be restored. Ensure that files in a file system have been properly stored or backed up before you delete the file system.
+ PrerequisitesThe 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 Available and Unavailable file systems can be deleted.
+
+ Figure 1 Deleting an SFS Turbo file system
+ - Check that the file system disappears from the file system list.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/sfs/umn/sfs_01_1001.html b/docs/sfs/umn/sfs_01_1001.html
new file mode 100644
index 00000000..9c330199
--- /dev/null
+++ b/docs/sfs/umn/sfs_01_1001.html
@@ -0,0 +1,200 @@
+
+
+ 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.
+
- 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:
rpm -qa|grep nfs
+ - In Debian or Ubuntu:
dpkg -l nfs-common
+
+If a command output similar to the following is displayed, the NFS software package has been installed and you can go to 4. If 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.
+
+- In CentOS, Red Hat, EulerOS, Fedora, or Oracle Enterprise Linux:
sudo yum -y install nfs-utils
+ - In Debian or Ubuntu:
sudo apt-get install nfs-common
+ - In SUSE or OpenSUSE:
zypper install 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 descriptionParameter
+ |
+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.
+ |
+
+
+
+
+ Figure 1 Mount point
+For more mounting parameters for performance optimization during file system mounting, see Table 2. Use commas (,) to separate parameters. The following command is an example:
+mount -t nfs -o vers=3,timeo=600,nolock,rsize=1048576,wsize=1048576,hard,retrans=3,noresvport,ro,async,noatime,nodiratime Mount point Local path
+
+Table 2 Parameters for file system mountingParameter
+ |
+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_01_1141.html b/docs/sfs/umn/sfs_01_1141.html
deleted file mode 100644
index b4889e17..00000000
--- a/docs/sfs/umn/sfs_01_1141.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
- How Do I Make the Most Out of My SFS Turbo File System?
- An SFS Turbo file system provides multiple IP addresses that can be used for mounting. Each IP address can be used by multiple clients. For the specific IP addresses, see the Alternative Shared Path field on the file system details page on the console.
- If the NFS protocol is used to access a file system, each client can only establish the network connection with one server. If you mount the file system using domain name, a random domain name server IP address is assigned. This may result in uneven distribution of network connections between clients and servers, and the distributed cluster capability of the servers cannot be fully used.
- When there are not too many clients and you want to maximize the file system performance, you can use different IP addresses when mounting the file system on different clients. In this way, the network connections between clients and servers are more evenly distributed, server resources are used more efficiently, and the file system performance can be fully used.
-
-
-
|
|---|
|
|
|---|
|---|
|
|---|
| |
Figure 2 SFS Turbo file system details-
. 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.
