You can search for file systems by file system name keyword or file system status, and view their basic information.
+You can search for a file system by name keyword or other properties, and view the file system 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 description Parameter
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
@@ -29,10 +34,10 @@File system protocol, which is NFS
Available Capacity (GB)
+Used Capacity (GB)
Remaining file system space available to data storage
-NOTE:This information is refreshed every 15 minutes.
+File system space already used for data storage
+NOTE:This information is refreshed every 15 minutes.
- Click the name of a file system to view detailed information about the file system. See Figure 1. -
- (Optional) Search for file systems by file system name keyword, key ID, or file system status.In the upper right corner of the page, click Search by Tag to query file systems by tag.diff --git a/docs/sfs/umn/en-us_topic_0034428727.html b/docs/sfs/umn/en-us_topic_0034428727.html index f9cb79b7..9a6fd259 100644 --- a/docs/sfs/umn/en-us_topic_0034428727.html +++ b/docs/sfs/umn/en-us_topic_0034428727.html @@ -36,7 +36,7 @@
- On the displayed Search by Tag tab page, enter a tag key and a tag value (must be among existing keys and values) and click Search.
- You can use more than one tag for a combination search. Each time after a key and a value are entered, click
. The added search criteria are displayed under the text boxes. When more than one tag is added, they will be applied together for a combination search. A maximum of 10 tags can be added at a time. - You can click Reset under the search criteria to reset.
- Click the name of a file system to view detailed information about the file system.
Figure 1 SFS Capacity-Oriented file system details+
Figure 2 SFS Turbo file system details+
- (Optional) Search for file systems by file system name keyword, key ID, or file system status.
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.
A geographical area with an independent network and an independent power supply.
You are advised to select the same AZ as that of the ECSs.
+You are advised to select the AZ where the servers reside.
Protocol Type
@@ -49,7 +49,7 @@VPC
An ECS cannot access file systems in a different VPC. Select the VPC to which the ECS belongs.
-NOTE:- By default, all ECSs in a VPC have the same rights. You can modify the VPC in the future.
- Upon creation, only one VPC can be added for each file system. After a file system is created, you can configure multiple VPCs by referring to Configuring Multi-VPC Access for the SFS file system.
NOTE:- By default, all ECSs in a VPC have the same rights. You can modify the VPC in the future.
- Only one VPC can be added for each file system during the creation. After a file system is created, you can configure multiple VPCs by referring to Configuring Multi-VPC Access for the SFS file system.
Click View VPC to view existing VPCs or create a new one.
@@ -57,7 +57,7 @@Maximum Capacity
Maximum capacity of a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system.
+Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity.
The value ranges from 1 GB to 512,000 GB.
Encryption
Optional
-This parameter specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system. If Encryption is selected, the following parameters will be displayed:
+Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system. If Encryption is selected, the following parameters will be displayed:
- Create Agency
If the KMS access rights are not granted to SFS Capacity-Oriented, this button will be displayed. Otherwise, this button will not be displayed.
Click Create Agency to grant SFS Capacity-Oriented the permissions to access KMS. The system automatically creates an agency and names it SFSAccessKMS. When SFSAccessKMS is displayed for Agency Name, the KMS access rights have been granted to SFS Capacity-Oriented, and SFS Capacity-Oriented can obtain KMS keys for encrypting or decrypting the file system. After the rights are granted, follow-up operations do not need granting rights again.
Optional
When creating a file system, you can bind tags to it. Tags are used to identify file system resources, and you can classify and search for file system resources by tag.
Tags are composed of key-value pairs.- Key: Mandatory if the file system is going to be tagged.
A tag key can contain a maximum of 36 characters. It can only contain letters, digits, hyphens (-), and underscores (_).
- - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters. It can only contain letters, digits, hyphens (-), and underscores (_).NOTE:@@ -116,114 +116,137 @@
- You can add a maximum of 10 tags to one file system.
- The tag keys of the same file system must be unique.
- Except for tagging the file system during disk creation, you can also add, modify, or delete tags for existing file systems.
- Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters. It can only contain letters, digits, hyphens (-), and underscores (_).
NOTE:- You can add a maximum of 10 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
Creating an SFS Turbo File System
- Log in to the management console using a cloud account.
- Log in to the management console and select a region and a project.
- Choose Storage > Scalable File Service.
- In the upper right corner of the page, click Create File System.
- Set the parameters on the page shown in Figure 2. Table 2 describes the parameters. +
- In the upper right corner of the page, click Create File System.
- Set the parameters on the page shown in Figure 2. Table 2 describes the parameters.
+
-
Table 2 Parameter description Parameter
+-Table 2 SFS Turbo file system parameters Parameter
Description
+Description
Remarks
+Remarks
File System Type
+Region
Mandatory
-Select SFS Capacity-Oriented or SFS Turbo.
+Mandatory
+Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
Select SFS Turbo.
+You are advised to select the region where the servers reside.
Region
+AZ
Mandatory
-Region of the tenant. Select the region from the drop-down list in the upper left corner of the page.
+Mandatory
+A geographical area with an independent network and an independent power supply.
You are advised to select the same region as that of the servers.
+You are advised to select the AZ where the servers reside.
AZ
+Type
Mandatory
-A geographical area with an independent network and an independent power supply.
+Mandatory
+The following types are supported: Standard, Standard - Enhanced, Performance, Performance-Enhanced, 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, and 250 MB/s/TiB.
+For more information, see File System Types.
You are advised to select the same AZ as that of the servers.
+After a file system is created, its type cannot be changed. To change the file system type, you need to create another file system. Plan your file system type in advance.
Protocol Type
+Capacity
Mandatory
-SFS Turbo supports NFS for file system access.
+Maximum capacity allowed for a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system capacity. The capacity of an SFS Turbo file system cannot be decreased. Set an appropriate file system capacity based on your service needs.
The default value is NFS.
+Supported scope:
+- 20 MB/s/TiB: 3.6 TB to 1 PB
- 40 MB/s/TiB: 1.2 TB to 1 PB
- 125 MB/s/TiB: 1.2 TB to 1 PB
- 250 MB/s/TiB: 1.2 TB to 1 PB
- Standard: 500 GB to 32 TB
- Performance: 500 GB to 32 TB
- Standard - Enhanced: 10 TB to 320 TB
- Performance - Enhanced: 10 TB to 320 TB
Storage Class
+Bandwidth (GB/s)
Mandatory
-Includes SFS Turbo Standard, SFS Turbo Standard – Enhanced, SFS Turbo Performance, and SFS Turbo Performance – Enhanced. For details about the features and application scenarios of each storage class, see File System Types.
+Defines the cache bandwidth, which is recommended for workloads with heavy reads and infrequent writes. The higher the bandwidth, the larger the capacity required.
Select Standard.
-NOTE:Once a file system is created, its storage class cannot be changed. If you want to change the storage class, you need to create another file system. Therefore, you are advised to plan the storage class carefully in advance.
+- If you select the 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, or 250 MB/s/TiB file system type, this parameter and its value will show up. Bandwidth size = Capacity x Bandwidth density (type value). The minimum bandwidth is 150 MB/s. If the calculated bandwidth is less than 150, 150 MB/s will be used.
- If you select the Standard, Standard - Enhanced, Performance, or Performance-Enhanced file system type, this parameter will not show up.
Protocol Type
+Mandatory
+SFS Turbo supports NFS for file system access.
+The default value is NFS.
+VPC
+Mandatory
+Select a VPC and a subnet.
+- VPC: A server cannot access file systems in a different VPC. Select the VPC to which the server belongs.
- Subnet: A subnet is a unique IP address range in a VPC. A subnet provides dedicated network resources that are logically isolated from other networks to improve network security.
NOTE:Only one VPC can be added for each file system during the creation. Multi-VPC file sharing can be implemented through VPC peering connection.
+For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
Capacity
-Maximum capacity of a single file system. When the used capacity of a file system reaches this value, no more data can be written to the file system. You need to expand the file system. The capacity of an SFS Turbo file system cannot be decreased. Set an appropriate file system capacity based on your service needs.
-Supported scope:
-- SFS Turbo Standard: 500 GB to 32 TB
- SFS Turbo Performance: 500 GB to 32 TB
- SFS Turbo Standard - Enhanced and SFS Turbo Performance - Enhanced: 10 TB to 320 TB.
-
VPC
+Cloud Backup and Recovery
Mandatory
-Select a VPC and its subnet.
-- VPC: A server cannot access file systems in a different VPC. Select the VPC to which the server belongs.
- Subnet: A subnet is an IP address range in a VPC. In a VPC, a subnet segment must be unique. A subnet provides dedicated network resources that are logically isolated from other networks, improving network security.
NOTE:-Upon creation, only one VPC can be added for each file system. Multi-VPC file sharing can be implemented through VPC peering connection.
-For details about VPC peering connection, see section "VPC Peering Connection" in Virtual Private Cloud User Guide.
--
-Security Group
-Mandatory
-A security group is a virtual firewall that provides secure network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group.
-When creating an SFS Turbo file system, you can select only one security group.
-You are advised to use an independent security group for an SFS Turbo instance to isolate it from service nodes.
-The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. 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 ECS 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.
--
-Encryption
-Optional
-This parameter specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system. If Encryption is selected, the following parameters will be displayed:
-- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see "Creating a CMK" in the Key Management Service User Guide.
- - KMS key ID
After you select a key name, the system automatically generates a key ID.
+Cloud Backup and Recovery (CBR) provides backup protection for SFS Turbo and allows you to use backup data to create SFS Turbo file systems. After you configure backup, the system will associate the SFS Turbo file system with the backup vault and apply the selected policy to the vault to periodically back up the file system.
+The following options are available, among which the default value is Not required:
+- Not required: Backup is not configured. If you need backup protection after a file system has been created, log in to the CBR console, locate the desired vault, and associate the file system with the vault.
- Use existing:
- Select an existing backup vault from the drop-down list.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
- Buy now:
- Enter a vault name, which can contain a maximum of 64 characters, including letters, digits, underscores (_), and hyphens (-), for example, vault-f61e. The default naming rule is vault_xxxx.
- Enter a vault capacity, which is required for backing up SFS Turbo file systems. The vault capacity cannot be less than the size of the file system. Its value ranges from the total size of the associated file systems to 10,485,760 in the unit of GB.
- Select a backup policy from the drop-down list, or go to the CBR console and configure a desired one.
-
+-
Name
+Encryption
Mandatory
-User-defined name of the file system.
+Optional
+Specifies whether a file system is encrypted. You can create a file system that is encrypted or not, but you cannot change the encryption settings of an existing file system. If Encryption is selected, the following parameters will be displayed:
+- KMS key name
KMS key name is the identifier of the key, and you can use KMS key name to specify the KMS key that is to be used for encryption. Select an existing key from the drop-down list, or click View KMS List to create a new key. For details, see "Creating a CMK" in the Key Management Service User Guide.
+ - KMS key ID
After you select a key name, the system automatically shows the key ID.
+ - Key Encryption Algorithm
After you select a key name, the system automatically shows the encryption algorithm of the key.
+
The value can contain only letters, digits, and hyphens (-). The name of the created file system must contain more than four characters and less than or equal to 64 characters.
+-
+Security Group
+Mandatory
+A security group is a virtual firewall that provides secure network access control policies for file systems. You can define different access rules for a security group to protect the file systems that are added to this security group.
+When creating an SFS Turbo file system, you can select only one security group.
+You are advised to use an independent security group for an SFS Turbo instance to isolate it from service nodes.
+The security group rule configuration affects the normal access and use of SFS Turbo. For details about how to configure a security group rule, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. Security Group button allows you to choose Security Group. Additionally you can choose whether 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 ECS and prevents file system mounting failures.
+-
+Tag
+Optional
+When creating a file system, you can bind tags to it. Tags are used to identify file system resources, and you can classify and search for file system resources by tag.
+Tags are composed of key-value pairs.+- Key: Mandatory if the file system is going to be tagged.
A tag key can contain a maximum of 36 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
+ - Value: Optional if the file system is going to be tagged. It can be an empty character string. A tag value can contain a maximum of 43 characters, including letters, digits, hyphens (-), underscores (_), and at signs (@).
- You can add a maximum of 20 tags to a file system.
- Tag keys of the same file system must be unique.
- Except for tagging the file system during file system creation, you can also add, modify, or delete tags for existing file systems.
Name
+Mandatory
+User-defined file system name.
+The name must start with a letter and can contain only letters, digits, and hyphens (-). It must contain more than four characters but no more than 64 characters.
- Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
+- Click Create Now.
- Confirm the file system information and click Submit.
- Complete the creation and go back to the file system list.
diff --git a/docs/sfs/umn/en-us_topic_0105224109.html b/docs/sfs/umn/en-us_topic_0105224109.html index 08dea5e0..333ca9b6 100644 --- a/docs/sfs/umn/en-us_topic_0105224109.html +++ b/docs/sfs/umn/en-us_topic_0105224109.html @@ -18,7 +18,7 @@If the status of the created file system is Available, the file system is created successfully. If the status is Creation failed, contact the administrator.
- Check that the IP address of the DNS server for resolving the domain names of the file systems has been configured on the ECS before mounting the file system. For details, see Configuring DNS. SFS Turbo file systems do not require domain name resolution.
- Run the following command in the Command Prompt of the Windows Server 2012 (X is the drive letter of the free disk). Select the ECS that belongs to the same VPC as the file system to mount the file system.
For SFS Capacity-Oriented file systems: mount -o nolock mount point X:
For SFS Turbo file systems: mount -o nolock -o casesensitive=yes IP address:/! X:
-
- Free drive letter of the disk: A drive letter that is not in use, such as driver letter E or X.
- The mount point of an SFS Turbo file system is the root directory. Ensure that an English exclamation mark (!) is added to the mount point, for example, 127.0.0.1:/!.
- casesensitive=yes indicates that file names are case sensitive during file search. If this parameter is not added, the performance of creating files in a large directory will deteriorate.
- Free drive letter of the disk: A drive letter that is not in use, such as drive letter E or X.
- The mount point of an SFS Turbo file system is the root directory. Ensure that an English exclamation mark (!) is added to the mount point, for example, 127.0.0.1:/!.
- casesensitive=yes indicates that file names are case sensitive during file search. If this parameter is not added, the performance of creating files in a large directory will deteriorate.
You can move the cursor to the mount point and click
next to the mount point to copy the mount point. For details, see Figure 8. If the information shown in Figure 9 is displayed, the mounting is successful.diff --git a/docs/sfs/umn/sfs_01_0005.html b/docs/sfs/umn/sfs_01_0005.html index fcec7a96..5dc9eb94 100644 --- a/docs/sfs/umn/sfs_01_0005.html +++ b/docs/sfs/umn/sfs_01_0005.html @@ -1,78 +1,232 @@File System Types
-SFS provides two types of file systems: SFS Capacity-Oriented and SFS Turbo. SFS Turbo is classified into SFS Turbo Standard, SFS Turbo Standard – Enhanced, SFS Turbo Performance, and SFS Turbo Performance – Enhanced.
+SFS provides two types of file systems: SFS Capacity-Oriented and SFS Turbo.
The following table describes the features, advantages, and application scenarios of these file system types.
- -Table 1 Comparison of file system types File System Type
++SFS Capacity-Oriented
++Table 1 SFS Capacity-Oriented file systems Parameter
Storage Class
-Feature
-Highlight
-Application Scenario
+SFS Capacity-Oriented
SFS Capacity-Oriented
+Max. bandwidth
-
-- Maximum bandwidth: 10 GB/s; maximum IOPS: 10,000
- With optimized features, it is suitable for services that require large capacity and high bandwidth.
- The maximum capacity can reach 2 PB, and the latency range is as follows:
- For sequential large I/Os of large files, the latency ranges from 20 ms to 50 ms.
- For sequential small I/Os of large files, the latency ranges from 10 ms to 20 ms.
- For random small I/Os of large files, the latency ranges from 200 ms to 500 ms.
NOTE:-- Latency refers to the minimum latency under low workload conditions. It is unstable.
- Large files refer to files larger than 10 MB, and large I/Os refer to I/Os larger than 1 MB.
Large capacity, high bandwidth, and low cost
-Cost-sensitive workloads which require large-capacity scalability, such as media processing, file sharing, HPC, and data backup. For workloads dealing with massive small files, SFS Turbo is recommended.
+10 GB/s
SFS Turbo
+Max. IOPS
SFS Turbo Standard
-- Maximum bandwidth: 120 MB/s; maximum IOPS: 3,000
- Latency: 10 to 20 ms; maximum capacity: 32 TB
- It is suitable for services with massive small files and services that require low latency.
Low latency and tenant exclusive
-Workloads dealing with massive small files, such as code storage, log storage, web services, and virtual desktop
+10,000
SFS Turbo Standard - Enhanced
+Latency
- Maximum bandwidth: 1 GB/s; maximum IOPS: 15,000
- Latency: 10 to 20 ms; maximum capacity: 320 TB
- Enhanced bandwidth, IOPS, and capacity
Low latency, high bandwidth, and tenant exclusive
-Workloads dealing with massive small files and those requiring high bandwidth, such as code storage, file sharing, enterprise office automation (OA), and log storage.
+Latency ranges:- For sequential large I/Os of large files, the latency ranges from 20 ms to 50 ms.
- For sequential small I/Os of large files, the latency ranges from 10 ms to 20 ms.
- For random small I/Os of large files, the latency ranges from 200 ms to 500 ms.
SFS Turbo Performance
+Max. capacity
- Maximum bandwidth: 320 MB/s; maximum IOPS: 20,000
- Latency: 6 to 10 ms; maximum capacity: 32 TB
- With optimized features, it is suitable for services with massive small files and services that require low latency and high IOPS.
Low latency, high IOPS, and tenant exclusive
-Workloads dealing with massive small files, and random I/O-intensive and latency-sensitive services, such as high-performance websites, file sharing, and content management
+2 PB
SFS Turbo Performance - Enhanced
+Highlights
- Maximum bandwidth: 2 GB/s; maximum IOPS: 100,000NOTE:-
Maximum performance can be reached with 5 ECSs in parallel which have recommended configuration c4.4xlarge.4.
- - Latency: 6 to 10 ms; maximum capacity: 320 TB
- Enhanced bandwidth, IOPS, and capacity
Large capacity, high bandwidth, and low cost
Low latency, high IOPS, high bandwidth, and tenant exclusive
+Use cases
Workloads dealing with massive small files, and latency-sensitive and bandwidth-demanding workloads, such as image rendering, AI training, and enterprise OA.
+Cost-sensitive workloads which require large-capacity scalability, such as media processing, file sharing, HPC, and data backup. For workloads dealing with massive small files, SFS Turbo is recommended.
+ - Latency refers to the minimum latency under low workload conditions. It is unstable.
- Large files refer to files larger than 10 MB, and large I/Os refer to I/Os larger than 1 MB.
SFS Turbo
++ +
+Table 2 SFS Turbo file systems Parameter
+20 MB/s/TiB
+40 MB/s/TiB
+125 MB/s/TiB
+250 MB/s/TiB
+Max. bandwidth
+8 GB/s
+8 GB/s
+20 GB/s
+20 GB/s
+Max. IOPS
+250,000
+250,000
+1 million
+1 million
+Single-queue, 4 KB latency
+2–5 ms
+2–5 ms
+1–3 ms
+1–3 ms
+Capacity
+3.6 TB to 1 PB
+1.2 TB to 1 PB
+1.2 TB to 1 PB
+1.2 TB to 1 PB
+IOPS calculation formula
+IOPS = Min. (250,000, 600 x Capacity)
+Capacity unit: TB
+IOPS = Min. (250,000, 1,200 x Capacity)
+Capacity unit: TB
+IOPS = Min. (1,000,000, 6,000 x Capacity)
+Capacity unit: TB
+IOPS = Min. (1,000,000, 12,500 x Capacity)
+Capacity unit: TB
+Highlights
+Large capacity and low cost
+Large capacity and low cost
+Low latency and cost effectiveness
+Low latency and cost effectiveness
+Typical use cases
+Log storage, file sharing, content management, and websites.
+Log storage, file sharing, content management, and websites.
+AI training, autonomous driving, EDA simulation, rendering, enterprise NAS, and HPC web applications.
+AI training, autonomous driving, EDA simulation, rendering, enterprise NAS, and HPC web applications.
++
+Table 3 Previous-generation SFS Turbo file systems Parameter
+Standard
+Standard - Enhanced
+Performance
+Performance - Enhanced
+Max. bandwidth
+120 MB/s
+1 GB/s
+320 MB/s
+2 GB/s
+Max. IOPS
+3,000
+15,000
+20,000
+100,000
+Single-queue, 4 KB latency
+2–5 ms
+2–5 ms
+1–3 ms
+1–3 ms
+Capacity
+500 GB to 32 TB
+10 TB to 320 TB
+500 GB to 32 TB
+10 TB to 320 TB
+Highlights
+Low latency and tenant exclusive
+Low latency, high bandwidth, and tenant exclusive
+Low latency, high IOPS, and tenant exclusive
+Low latency, high IOPS, high bandwidth, and tenant exclusive
+Typical use cases
+Code storage, file sharing, enterprise OA, and log storage.
+Code storage, file sharing, enterprise OA, and log storage.
+HPC websites, file sharing, content management, image rendering, AI training, and enterprise OA.
+HPC websites, file sharing, content management, image rendering, AI training, and enterprise OA.
++ - 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.
diff --git a/docs/sfs/umn/sfs_01_0007.html b/docs/sfs/umn/sfs_01_0007.html index 8d5184c7..bd455012 100644 --- a/docs/sfs/umn/sfs_01_0007.html +++ b/docs/sfs/umn/sfs_01_0007.html @@ -40,7 +40,7 @@Once you have subscribed to SFS, you can monitor its performance, such as the read bandwidth, write bandwidth, and read write bandwidth on Cloud Eye, which does not require any plug-ins.
+Once you have subscribed to SFS, you can monitor its performance, such as the read bandwidth, write bandwidth, and read and write bandwidth on Cloud Eye, which does not require any plug-ins.
Cloud Eye
File System Resizing
-Scenarios
You can expand or shrink the capacity of a file system when needed.
Limitations and Constraints
The capacity of an SFS Turbo file system can be expanded but cannot be shrunk.
+Limitations and Constraints
The 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.
-Rules for Resizing
The 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 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, 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 the new capacity to be smaller than 10 TB.
+ - 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.
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. See Figure 1. -
- Enter a new maximum capacity of the file system based on service requirements, and click OK. Table 1 describes the parameters.
-
Table 1 Parameter description Parameter
+diff --git a/docs/sfs/umn/sfs_01_0044.html b/docs/sfs/umn/sfs_01_0044.html index 5129b46c..9b14ece6 100644 --- a/docs/sfs/umn/sfs_01_0044.html +++ b/docs/sfs/umn/sfs_01_0044.html @@ -11,8 +11,8 @@Procedure
- Log in to the SFS console.
- In the file system list, click Resize or Expand Capacity in the row of the desired file system, as shown in Figure 1.
+Figure 2 Expanding an SFS Turbo file system+
- Enter a new capacity and click OK. The following tables describe the parameters.
+
+ +Table 1 SFS Capacity-Oriented file system resizing parameters Parameter
Description
+Description
Used Capacity (GB)
+Used Capacity (GB)
Used capacity of the current file system
+Used capacity of the current file system
Maximum Capacity (GB)
+Maximum Capacity (GB)
Maximum capacity of the current file system
+Maximum capacity of the current file system
New Maximum Capacity (GB)
+New Maximum Capacity (GB)
Target maximum capacity of the file system after expanding or shrinking The value ranges from 1 GB to 512,000 GB.
-NOTE:The new maximum capacity cannot be smaller than the used capacity.
+Target maximum capacity of the file system after expanding or shrinking The value ranges from 1 GB to 512,000 GB.
+NOTE:The new maximum capacity cannot be smaller than the used capacity.
+Table 2 SFS Turbo file system capacity expansion parameters Parameter
+Description
+Current Capacity
+Current storage capacity of the file system
+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.
- In the displayed dialog box, confirm the information and click OK.
- In the file system list, check the capacity information after resizing.
Using a Backup to Create a File System
In case of a virus attack, accidental deletion, or software or hardware fault, you can use an SFS Turbo file system backup to create a new file system. Data on the new file system is the same as that in the backup.
- Log in to CBR Console.
- Log in to the management console.
- Click
in the upper left corner and select your desired region and project. - Choose Storage > Cloud Backup and Recovery > SFS Turbo Backups.
- Click the Backups tab and locate the desired backup.
- If the status of the target backup is Available, click Create File System in the Operation column of the backup.
- Set the file system parameters. See Figure 1.
-
- For detailed parameter descriptions, see table "Parameter description" under "Creating an SFS Turbo File System".
- 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. +
- For detailed parameter descriptions, see table "Parameter description" under Creating an SFS Turbo File System.
- Click Next.
- Go back to the file system list and check whether the file system is successfully created.
diff --git a/docs/sfs/umn/sfs_01_0091.html b/docs/sfs/umn/sfs_01_0091.html index bb1c529e..08badc1a 100644 --- a/docs/sfs/umn/sfs_01_0091.html +++ b/docs/sfs/umn/sfs_01_0091.html @@ -12,6 +12,8 @@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.
- How Is the SFS Turbo Capacity Quota Calculated?
+
- How Do I Make the Most Out of My SFS Turbo File System?
+diff --git a/docs/sfs/umn/sfs_01_0104.html b/docs/sfs/umn/sfs_01_0104.html index 38a5b5ca..c6e4faa1 100644 --- a/docs/sfs/umn/sfs_01_0104.html +++ b/docs/sfs/umn/sfs_01_0104.html @@ -8,7 +8,13 @@
2023-08-29
+2024-07-30
+Updated the following content:
+- Added descriptions about the 20 MB/s/TiB, 40 MB/s/TiB, 125 MB/s/TiB, and 250 MB/s/TiB SFS Turbo file system types.
- Updated section Create a File System.
- Updated section Viewing a File System.
- Updated section File System Resizing.
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.
diff --git a/docs/sfs/umn/sfs_01_1141.html b/docs/sfs/umn/sfs_01_1141.html new file mode 100644 index 00000000..b4889e17 --- /dev/null +++ b/docs/sfs/umn/sfs_01_1141.html @@ -0,0 +1,13 @@ + + +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.
+++++Parent topic: Others+
