Disk type
diff --git a/docs/evs/umn/evs_01_0026.html b/docs/evs/umn/evs_01_0026.html
index 24d4d95b..7131989a 100644
--- a/docs/evs/umn/evs_01_0026.html
+++ b/docs/evs/umn/evs_01_0026.html
@@ -9,7 +9,7 @@
ProcedureThe following operations are for reference only. For details, see Assigning a Virtual IP Address in the Virtual Private Cloud User Guide.
- - Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - Under Computing, click Elastic Cloud Server.
The Elastic Cloud Server page is displayed.
+- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Compute, click Elastic Cloud Server.
The Elastic Cloud Server page is displayed.
- In the ECS list, locate the production ECS and click the ECS name.
The ECS details page is displayed.
- On the ECS details page, locate the VPC and click the VPC name.
The Virtual Private Cloud page is displayed.
- In the VPC list, locate the VPC of the production ECS and click the VPC name.
The VPC details page is displayed.
@@ -19,21 +19,21 @@
- If no, perform the following operations:
- Click Assign Virtual IP Address.
After the application succeeds, you can view the virtual IP address in the virtual IP address list.
 When assigning the virtual IP address, you can select the Automatic or Manual mode based on your service requirements.
- Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the production server.
After the virtual IP address is bound with the production server, the subnet details page is displayed.
- - Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.
After the virtual IP address is bound with the DR server, the subnet details page is displayed.
+ - Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the production server.
After the virtual IP address is bound with the production server, the subnet details page is displayed.
+ - Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.
After the virtual IP address is bound with the DR server, the subnet details page is displayed.
- On the subnet details page, take note of the subnet and the IP address of the server's NIC where the virtual IP address has been bound.
An example is provided as follows: - Subnet: 192.168.0.0/24
- Bound server (NIC): ecs-001 (192.168.0.176)
- After a virtual IP address is bound with a server, perform the following substeps to configure the bound IP address as the static IP address:
The following example uses CentOS 7.2 64bit as the sample OS. The configuration method varies depending on the server OS. This document is used for reference only. For the detailed operations and differences, see the corresponding OS documents.
+ - After a virtual IP address is bound with a server, perform the following substeps to configure the bound IP address as the static IP address:
The following example uses CentOS 7.2 64bit as the sample OS. The configuration method varies depending on the server OS. This document is used for reference only. For detailed operations and differences, see the corresponding OS documents.
For the Windows OS, see the Microsoft official documentation.
- Log in to the server as user root.
- Run the following command to check the name of the NIC bound with the virtual IP address in the server:
ifconfig
You can obtain the NIC name using the NIC IP address recorded in 9. In this example, the NIC name is eth0.
- Run the following command to switch to the directory containing NIC configuration files:
cd /etc/sysconfig/network-scripts
- Run the following command to copy NIC configuration file eth0 and change its name to eth0:1:
cp eth0 eth0:1
- - Perform the following operations to modify the configuration parameters of eth0:1 using the vi editor:
- Run the following command to open the ifcfg-eth0:1 file:
vi ifcfg-eth0:1
- - Press i to enter editing mode.
- Configure the parameters according to the following example:
BOOTPROTO=static
+ - Perform the following operations to modify the configuration parameters of eth0:1 using the vi editor:
- Run the following command to open the ifcfg-eth0:1 file:
vi ifcfg-eth0:1
+ - Press i to enter editing mode.
- Configure the parameters according to the following example:
BOOTPROTO=static
DEVICE=eth0:1
NAME=eth0:1
ONBOOT=yes
@@ -41,29 +41,29 @@ TYPE=Ethernet
USERCTL=no
IPADDR=192.168.0.176
NETMASK=255.255.255.0
-Configuration descriptions of the NAME, IPADDR, and NETMASK fields: - NAME: Specifies the NIC name recorded in 10.b.
- IPADDR: Specifies the NIC IP address recorded in 9.
- NETMASK: Specifies the subnet recorded in 9.
In this example, the subnet mask has 24 bits. Therefore, enter 255.255.255.0 for NETMASK.
+Configuration descriptions of the NAME, IPADDR, and NETMASK fields:
- Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
+ - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- Run the following command to delete unnecessary NIC files from the /etc/sysconfig/network-scripts directory:
rm Name of the unnecessary NIC file
-For example, run the following command:
+In this example, run the following commands:
rm ifcfg-eth1
Before deleting the unnecessary NIC files, you are advised to back up the files.
If multiple unnecessary NIC files exist, delete them individually. Ensure that the /etc/sysconfig/network-scripts directory contains only the in-use NIC file.
- - Run the following command to check whether the 70-persistent-ipoib.rules file exists in the /etc/udev/rules.d/ directory:
ls /etc/udev/rules.d/70-persistent-ipoib.rules- If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.
- Run the following command to open the 70-persistent-ipoib.rules file:
vi /etc/udev/rules.d/70-persistent-ipoib.rules
- - Press i to enter editing mode.
- Add NIC information for the DR server based on that of the production server. For details, see the following example:
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0"
+ - Run the following command to check whether the 70-persistent-ipoib.rules file exists in the /etc/udev/rules.d/ directory:
ls /etc/udev/rules.d/70-persistent-ipoib.rules- If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.
- Run the following command to open the 70-persistent-ipoib.rules file:
vi /etc/udev/rules.d/70-persistent-ipoib.rules
+ - Press i to enter editing mode.
- Add NIC information for the DR server based on that of the production server. For details, see the following example:
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0"
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"
-Configuration descriptions of the ATTR{address} and NAME fields:
-- ATTR{address}: specifies the MAC address of server's NIC.
- NAME: Specifies the NIC name recorded in 10.b.
a. Ensure that the NAME (NIC name) values of the production and DR servers are consistent. The ATTR{address} (MAC address) value can be obtained in Collecting ECS Information (Deprecated).
+ Configuration descriptions of the ATTR{address} and NAME fields:
+ - ATTR{address}: specifies the MAC address of server's NIC.
- NAME: Specifies the NIC name recorded in 10.b.
a. Ensure that the NAME (NIC name) values of the production and DR servers are consistent. The ATTR{address} (MAC address) value can be obtained in Collecting ECS Information (Deprecated).
b. Replace {mac} with the MAC address during operation.
- - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
+ - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- If no, go to 10.h.
diff --git a/docs/evs/umn/evs_01_0033.html b/docs/evs/umn/evs_01_0033.html
index 86bb6477..a97774fa 100644
--- a/docs/evs/umn/evs_01_0033.html
+++ b/docs/evs/umn/evs_01_0033.html
@@ -1,19 +1,22 @@
Initializing a Linux Data Disk (fdisk)
- ScenariosThis section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.
- The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
- The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
- The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
+ ScenariosThis section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.
+ The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
+ The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
+ The method for initializing a disk varies slightly depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
+  When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
+
- Prerequisites- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
+Prerequisites- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Creating and Mounting a PartitionThe following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured with automatic mounting at system start.
+ Creating and Mounting a PartitionThe following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
- - fdisk -l
Information similar to the following is displayed: [root@ecs-test-0001 ~]# fdisk -l
+- Query what block devices are available on the server.
fdisk -l
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# fdisk -l
-Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Disk /dev/vda: 42.9 GiB, 42949672960 bytes, 83886080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
@@ -23,16 +26,16 @@ Disk identifier: 0x000bcb4e
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 83886079 41942016 83 Linux
-Disk /dev/vdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Disk /dev/vdb: 107.4 GiB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
In the command output, the server contains two disks. /dev/vda is the system disk, and /dev/vdb is the new data disk.
- - Run the following command to enter fdisk to partition the new data disk:
fdisk New data disk
-In this example, run the following command:
-fdisk /dev/vdb
-Information similar to the following is displayed: [root@ecs-test-0001 ~]# fdisk /dev/vdb
+In the command output, this server contains two disks: /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
+ - Launch fdisk to partition the new data disk.
fdisk New data disk
+In this example, run the following command:
+fdisk /dev/vdb
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# fdisk /dev/vdb
Welcome to fdisk (util-linux 2.23.2).
Changes will remain in memory only, until you decide to write them.
@@ -43,41 +46,41 @@ Building a new DOS disklabel with disk identifier 0x38717fc1.
Command (m for help):
- Enter n and press Enter to create a new partition.
Information similar to the following is displayed: Command (m for help): n
+ - Enter n and press Enter to create a new partition.
Information similar to the following is displayed: Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
There are two types of disk partitions: - Choosing p creates a primary partition.
- Choosing e creates an extended partition.
- If the MBR partition style is used, a maximum of 4 primary partitions, or 3 primary partitions and 1 extended partition can be created. The extended partition cannot be used directly and must be divided into logical partitions before use.
- Disk partitions created using GPT are not categorized.
+ There are two types of disk partitions: - Choosing p creates a primary partition.
- Choosing e creates an extended partition.
+ If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.
+ Disk partitions created using GPT are not categorized.
- - In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.
Information similar to the following is displayed: Select (default p): p
+ - Enter p and press Enter to create a primary partition in this example.
Information similar to the following is displayed: Select (default p): p
Partition number (1-4, default 1):
Partition number indicates the serial number of the primary partition. The value ranges from 1 to 4.
- - Enter the serial number of the primary partition and press Enter. Primary partition number 1 is used in this example. One usually starts with partition number 1 when partitioning an empty disk.
Information similar to the following is displayed: Partition number (1-4, default 1): 1
+Partition number indicates the serial number of the primary partition. The value ranges from 1 to 4.
+ - Enter the serial number of the primary partition and press Enter. Primary partition number 1 is used in this example. One usually starts with partition number 1 when partitioning an empty disk.
Information similar to the following is displayed: Partition number (1-4, default 1): 1
First sector (2048-209715199, default 2048):
First sector indicates the start sector. The value ranges from 2048 to 209715199, and the default value is 2048.
- - Select the default start sector 2048 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
-Information similar to the following is displayed: First sector (2048-209715199, default 2048):
+First sector indicates the start sector. The value ranges from 2048 to 209715199, and the default value is 2048.
+ - Select the default start sector 2048 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
+Information similar to the following is displayed: First sector (2048-209715199, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.
- - Select the default end sector 209715199 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
-Information similar to the following is displayed:
-Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
+Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.
+ - Select the default end sector 209715199 and press Enter.
The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.
+Information similar to the following is displayed:
+Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
Using default value 209715199
Partition 1 of type Linux and of size 100 GiB is set
Command (m for help):
-A primary partition has been created for the new data disk.
- - Enter p and press Enter to view details about the new partition.
Information similar to the following is displayed: Command (m for help): p
+A primary partition has been created for the new data disk.
+ - Enter p and press Enter to print the partition details.
Information similar to the following is displayed: Command (m for help): p
-Disk /dev/vdb: 107.4 GB, 107374182400 bytes, 209715200 sectors
+Disk /dev/vdb: 107.4 GiB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
@@ -89,21 +92,21 @@ Disk identifier: 0x38717fc1
Command (m for help):
Details about the /dev/vdb1 partition are displayed.
- - Enter w and press Enter to write the changes to the partition table.
Information similar to the following is displayed: Command (m for help): w
+Details about the /dev/vdb1 partition are displayed.
+ - Enter w and press Enter to write the changes to the partition table.
Information similar to the following is displayed: Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
The partition is created.
- In case that you want to discard the changes made before, you can exit fdisk by entering q.
+ The partition is created.
+ In case that you want to discard the changes made before, you can exit fdisk by entering q.
- - Run the following command to synchronize the new partition table to the OS:
partprobe
- - Run the following command to set the file system format for the new partition:
mkfs -t File system format /dev/vdb1
-In this example, run the following command to set the ext4 file system for the new partition:
-mkfs -t ext4 /dev/vdb1
-Information similar to the following is displayed: [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
+ - Synchronize the new partition table to the OS.
partprobe
+ - Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
+In this example, the ext4 format is used for the new partition.
+mkfs -t ext4 /dev/vdb1
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
@@ -126,20 +129,20 @@ Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
The formatting takes a period of time. Observe the system running status and do not exit.
- The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.
+ The formatting takes a period of time. Observe the system running status and do not exit.
+ The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- - Run the following command to create a mount point:
mkdir Mount point
-In this example, run the following command to create the /mnt/sdc mount point:
-mkdir /mnt/sdc
- The /mnt directory exists on all Linux systems. If the mount point fails to create, it may be that the /mnt directory has been accidentally deleted. Run the mkdir -p /mnt/sdc command to create the mount point.
+ - Create a mount point.
mkdir Mount point
+In this example, the /mnt/sdc mount point is created.
+mkdir /mnt/sdc
+ The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
- - Run the following command to mount the new partition on the created mount point:
mount Disk partition Mount point
-In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:
-mount /dev/vdb1 /mnt/sdc
- - Run the following command to view the mount result:
df -TH
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# df -TH
+ - Mount the new partition on the created mount point.
mount Disk partition Mount point
+In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
+mount /dev/vdb1 /mnt/sdc
+ - Check the mount result.
df -TH
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# df -TH
Filesystem Type Size Used Avail Use% Mounted on
/dev/vda1 ext4 43G 1.9G 39G 5% /
devtmpfs devtmpfs 2.0G 0 2.0G 0% /dev
@@ -148,33 +151,33 @@ tmpfs tmpfs 2.0G 9.1M 2.0G 1% /run
tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs tmpfs 398M 0 398M 0% /run/user/0
/dev/vdb1 ext4 106G 63M 101G 1% /mnt/sdc
-New partition /dev/vdb1 is mounted on /mnt/sdc.
- If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.
+ You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
+
- Setting Automatic Mounting at System StartModify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.
- The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.
- UUID is the unique character string for disk partitions in a Linux system.
+ Configuring Automatic Mounting at System StartThe fstab file controls what disks are automatically mounted at startup. You can use fstab to configure your data disks to mount automatically. This operation will not affect the existing data.
+ The example here uses UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent the server from booting up.
+ UUIDs are the unique character strings for identifying partitions in Linux.
- - Run the following command to query the partition UUID:
blkid Disk partition
-In this example, run the following command to query the UUID of the /dev/vdb1 partition:
-blkid /dev/vdb1
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# blkid /dev/vdb1
+- Query the partition UUID.
blkid Disk partition
+In this example, the UUID of the /dev/vdb1 partition is queried.
+blkid /dev/vdb1
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# blkid /dev/vdb1
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
-The UUID of the /dev/vdb1 partition is displayed.
- - Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
- - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
- - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- - Perform the following operations to verify the automatic mounting function:
- Run the following command to unmount the partition:
umount Disk partition
-In this example, run the following command:
-umount /dev/vdb1
- - Run the following command to reload all the content in the /etc/fstab file:
mount -a
- - Run the following command to query the file system mounting information:
mount | grep Mount point
-In this example, run the following command:
-mount | grep /mnt/sdc
-If information similar to the following is displayed, automatic mounting has been configured:
-root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+Carefully record the UUID, as you will need it for the following step.
+ - Open the fstab file using the vi editor.
vi /etc/fstab
+ - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
+ - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
+ - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
umount Disk partition
+In this example, run the following command:
+umount /dev/vdb1
+ - Reload all the content in the /etc/fstab file.
mount -a
+ - Query the file system mounting information.
mount | grep Mount point
+In this example, run the following command:
+mount | grep /mnt/sdc
+If information similar to the following is displayed, automatic mounting has been configured:
+root@ecs-test-0001 ~]# mount | grep /mnt/sdc
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
diff --git a/docs/evs/umn/evs_01_0034.html b/docs/evs/umn/evs_01_0034.html
index a493a72a..c70710d9 100644
--- a/docs/evs/umn/evs_01_0034.html
+++ b/docs/evs/umn/evs_01_0034.html
@@ -1,53 +1,55 @@
Initializing a Linux Data Disk (parted)
-ScenariosThis section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.
- The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
- The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
- The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
+ ScenariosThis section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.
+ The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.
+ The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
+ The method for initializing a disk varies slightly depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.
+ When using a disk for the first time, if you have not initialized it, including creating partitions and file systems, the additional space added to this disk in an expansion later may not be normally used.
+
- Prerequisites- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
+Prerequisites- A data disk has been attached to a server and has not been initialized.
- You have logged in to the server.
- For how to log in to an ECS, see the Elastic Cloud Server User Guide.
- For how to log in to a BMS, see the Bare Metal Server User Guide.
Creating and Mounting a PartitionThe following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured with automatic mounting at system start.
+ Creating and Mounting a PartitionThe following example shows you how a new partition can be created on a new data disk that has been attached to a server. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on /mnt/sdc, and configured to mount automatically at startup.
- - Run the following command to query information about the new data disk:
lsblk
-Information similar to the following is displayed: root@ecs-test-0001 ~]# lsblk
+- Query information about the new data disk.
lsblk
+Information similar to the following is displayed: root@ecs-test-0001 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 40G 0 disk
└─vda1 253:1 0 40G 0 part /
vdb 253:16 0 100G 0 disk
In the command output, the server contains two disks. /dev/vda is the system disk, and /dev/vdb is the new data disk.
- - Run the following command to enter parted to partition the new data disk:
parted New data disk
-In this example, run the following command:
-parted /dev/vdb
-Information similar to the following is displayed: [root@ecs-test-0001 ~]# parted /dev/vdb
+In the command output, this server contains two disks. /dev/vda and /dev/vdb. /dev/vda is the system disk, and /dev/vdb is the new data disk.
+ - Launch parted to partition the new data disk.
parted New data disk
+In this example, run the following command:
+parted /dev/vdb
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# parted /dev/vdb
GNU Parted 3.1
Using /dev/vdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
- Enter p and press Enter to view the current disk partition style.
Information similar to the following is displayed: (parted) p
+ - Enter p and press Enter to view the current disk partition style.
Information similar to the following is displayed: (parted) p
Error: /dev/vdb: unrecognised disk label
Model: Virtio Block Device (virtblk)
-Disk /dev/vdb: 107GB
+Disk /dev/vdb: 107GiB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
(parted)
In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.
- - Run the following command to set the disk partition style:
mklabel Disk partition style
-In this example, run the following command to set the partition style to GPT: (Disk partition styles can be MBR or GPT.)
-mklabel gpt
- The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.
- If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
+ In the command output, the Partition Table value is unknown, indicating that no partition style is set for the new disk.
+ - Set the disk partition style.
mklabel Disk partition style
+This command lets you control whether to use MBR or GPT for your partition table. In this example, GPT is used.
+mklabel gpt
+ The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.
+ If the partition style is changed after the disk has been used, all data on the disk will be lost, so take care to select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.
- - Enter p and press Enter to view the disk partition style.
Information similar to the following is displayed: (parted) mklabel gpt
+ - Enter p and press Enter to view the disk partition style.
Information similar to the following is displayed: (parted) mklabel gpt
(parted) p
Model: Virtio Block Device (virtblk)
-Disk /dev/vdb: 107GB
+Disk /dev/vdb: 107GiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
@@ -56,15 +58,15 @@ Number Start End Size File system Name Flags
(parted)
In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.
- - Enter unit s and press Enter to set the measurement unit of the disk to sector.
- Run the following command and press Enter:
mkpart Partition name Start sector End sector
-In this example, run the following command:
-mkpart test 2048s 100%
-In this example, one partition is created for the new data disk. Variable 2048s indicates the disk start sector, and variable 100% indicates the disk end sector. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.
-Information similar to the following is displayed: (parted) mkpart opt 2048s 100%
+In the command output, the Partition Table value is gpt, indicating that the disk partition style is GPT.
+ - Enter unit s and press Enter to set the measurement unit of the disk to sector.
- Create a new partition.
mkpart Partition name Start sector End sector
+In this example, run the following command:
+mkpart test 2048s 100%
+In this example, one partition is created for the new data disk, starting on 2048 and using 100% of the rest of the disk. The two values are used for reference only. You can determine the number of partitions and the partition size based on your service requirements.
+Information similar to the following is displayed: (parted) mkpart opt 2048s 100%
(parted)
- Enter p and press Enter to view details about the new partition.
Information similar to the following is displayed: (parted) p
+ - Enter p and press Enter to print the partition details.
Information similar to the following is displayed: (parted) p
Model: Virtio Block Device (virtblk)
Disk /dev/vdb: 209715200s
Sector size (logical/physical): 512B/512B
@@ -76,23 +78,23 @@ Number Start End Size File system Name Flags
(parted)
- Enter q and press Enter to exit parted.
Information similar to the following is displayed: (parted) q
+ - Enter q and press Enter to exit parted.
Information similar to the following is displayed: (parted) q
Information: You may need to update /etc/fstab.
You can set automatic disk mounting by updating the /etc/fstab file. Before updating the file, set the file system format for the partition and mount the partition on the mount point.
- - Run the following command to view the disk partition information:
lsblk
-Information similar to the following is displayed: [root@ecs-test-0001 ~]# lsblk
+You can configure automatic mounting by updating the /etc/fstab file. Before doing so, format the partition with a desired file system and mount the partition on the mount point.
+ - View the disk partition information.
lsblk
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 40G 0 disk
└─vda1 253:1 0 40G 0 part /
vdb 253:16 0 100G 0 disk
└─vdb1 253:17 0 100G 0 part
In the command output, /dev/vdb1 is the partition you created.
- - Run the following command to set the file system format for the new partition:
mkfs -t File system format /dev/vdb1
-In this example, run the following command to set the ext4 file system for the new partition:
-mkfs -t ext4 /dev/vdb1
-Information similar to the following is displayed: [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
+In the command output, /dev/vdb1 is the partition you created.
+ - Format the new partition with a desired file system format.
mkfs -t File system format /dev/vdb1
+In this example, the ext4 format is used for the new partition.
+mkfs -t ext4 /dev/vdb1
+Information similar to the following is displayed: [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb1
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
@@ -115,20 +117,20 @@ Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
The formatting takes a period of time. Observe the system running status and do not exit.
- The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.
+ The formatting takes a period of time. Observe the system running status and do not exit.
+ The partition sizes supported by file systems vary. Choose an appropriate file system format based on your service requirements.
- - Run the following command to create a mount point:
mkdir Mount point
-In this example, run the following command to create the /mnt/sdc mount point:
-mkdir /mnt/sdc
- The /mnt directory exists on all Linux systems. If the mount point fails to create, it may be that the /mnt directory has been accidentally deleted. Run the mkdir -p /mnt/sdc command to create the mount point.
+ - Create a mount point.
mkdir Mount point
+In this example, the /mnt/sdc mount point is created.
+mkdir /mnt/sdc
+ The /mnt directory exists on all Linux systems. If the mount point cannot be created, it may be that the /mnt directory has been accidentally deleted. You can run mkdir -p /mnt/sdc to create the mount point.
- - Run the following command to mount the new partition on the created mount point:
mount Disk partition Mount point
-In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:
-mount /dev/vdb1 /mnt/sdc
- - Run the following command to view the mount result:
df -TH
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# df -TH
+ - Mount the new partition on the created mount point.
mount Disk partition Mount point
+In this example, the /dev/vdb1 partition is mounted on /mnt/sdc.
+mount /dev/vdb1 /mnt/sdc
+ - Check the mount result.
df -TH
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# df -TH
Filesystem Type Size Used Avail Use% Mounted on
/dev/vda1 ext4 43G 1.9G 39G 5% /
devtmpfs devtmpfs 2.0G 0 2.0G 0% /dev
@@ -137,33 +139,33 @@ tmpfs tmpfs 2.0G 9.0M 2.0G 1% /run
tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
tmpfs tmpfs 398M 0 398M 0% /run/user/0
/dev/vdb1 ext4 106G 63M 101G 1% /mnt/sdc
-New partition /dev/vdb1 is mounted on /mnt/sdc.
- If the server is restarted, the mounting will become invalid. You can set automatic mounting for partitions at system start by modifying the /etc/fstab file. For details, see Setting Automatic Mounting at System Start.
+ You should now see that partition /dev/vdb1 is mounted on /mnt/sdc.
+
- Setting Automatic Mounting at System StartModify the fstab file to set automatic disk mounting at server start. You can also set automatic mounting for the servers containing data. This operation will not affect the existing data.
- The following procedure shows how to set automatic disk mounting at server start by using UUIDs to identify disks in the fstab file. You are advised not to use device names to identify disks in the file because a device name may change (for example, from /dev/vdb1 to /dev/vdb2) during the server stop or start, resulting in improper server running after restart.
- UUID is the unique character string for disk partitions in a Linux system.
+ Configuring Automatic Mounting at System StartThe fstab file controls what disks are automatically mounted at server startup. You can configure the fstab file of a server that has data. This operation will not affect the existing data.
+ The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent your server from booting up.
+ UUIDs are the unique character strings for identifying partitions in Linux.
- - Run the following command to query the partition UUID:
blkid Disk partition
-In this example, run the following command to query the UUID of the /dev/vdb1 partition:
-blkid /dev/vdb1
-Information similar to the following is displayed:
-[root@ecs-test-0001 ~]# blkid /dev/vdb1
+- Query the partition UUID.
blkid Disk partition
+In this example, the UUID of the /dev/vdb1 partition is queried.
+blkid /dev/vdb1
+Information similar to the following is displayed:
+[root@ecs-test-0001 ~]# blkid /dev/vdb1
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
-The UUID of the /dev/vdb1 partition is displayed.
- - Run the following command to open the fstab file using the vi editor:
vi /etc/fstab
- - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
- - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
- - Perform the following operations to verify the automatic mounting function:
- Run the following command to unmount the partition:
umount Disk partition
-In this example, run the following command:
-umount /dev/vdb1
- - Run the following command to reload all the content in the /etc/fstab file:
mount -a
- - Run the following command to query the file system mounting information:
mount | grep Mount point
-In this example, run the following command:
-mount | grep /mnt/sdc
-If information similar to the following is displayed, automatic mounting has been configured:
-root@ecs-test-0001 ~]# mount | grep /mnt/sdc
+Carefully record the UUID, as you will need it for the following step.
+ - Open the fstab file using the vi editor.
vi /etc/fstab
+ - Press i to enter editing mode.
- Move the cursor to the end of the file and press Enter. Then, add the following information:
UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2
+ - Press Esc, enter :wq, and press Enter.
The system saves the configurations and exits the vi editor.
+ - Verify that the disk is auto-mounted at startup.
- Unmount the partition.
umount Disk partition
+In this example, run the following command:
+umount /dev/vdb1
+ - Reload all the content in the /etc/fstab file.
mount -a
+ - Query the file system mounting information.
mount | grep Mount point
+In this example, run the following command:
+mount | grep /mnt/sdc
+If information similar to the following is displayed, automatic mounting has been configured:
+root@ecs-test-0001 ~]# mount | grep /mnt/sdc
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
diff --git a/docs/evs/umn/evs_01_0035.html b/docs/evs/umn/evs_01_0035.html
index 62367144..c53d8345 100644
--- a/docs/evs/umn/evs_01_0035.html
+++ b/docs/evs/umn/evs_01_0035.html
@@ -74,10 +74,12 @@ vdb 253:16 0 150G 0 disk
└─vdb1 253:17 0 100G 0 part /mnt/sdc
In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, /dev/vdb has 150 GiB, and /dev/vdb1 has 100 GiB.
+
- Run the following command to view the current disk partition style:
fdisk -l
Information similar to the following is displayed: [root@ecs-test-0001 ~]# fdisk -l
-Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
+Disk /dev/vda: 42.9 GiB, 42949672960 bytes, 83886080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
@@ -87,7 +89,7 @@ Disk identifier: 0x000bcb4e
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 83886079 41942016 83 Linux
-Disk /dev/vdb: 161.1 GB, 161061273600 bytes, 314572800 sectors
+Disk /dev/vdb: 161.1 GiB, 161061273600 bytes, 314572800 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
@@ -98,10 +100,12 @@ Disk identifier: 0x38717fc1
/dev/vdb1 2048 209715199 104856576 83 Linux
The value in the System column indicates the disk partition style. Value Linux indicates the MBR partition style. Value GPT indicates the GPT partition style.
-- If the disk partitions displayed are inconsistent with those obtained in 1, the partition that is not displayed uses the GPT partition style and has unallocated space. In this case, you cannot query all the partition information using the fdisk -l command. Go to Method 2: Check Partition Style and File System Format Using parted.
- If the disk partitions displayed are consistent with those obtained in 1, continue with the following operations.
+- If the disk partitions displayed are inconsistent with those obtained in 1, the possible reason may be that existing partitions uses GPT and there is unallocated disk space. In this case, you cannot query all the partitions using fdisk -l. Go to Method 2: Check Partition Style and File System Format Using parted.
- If the disk partitions displayed are consistent with those obtained in 1, continue with the following operations.
- Run the following command to view the partition's file system format:
blkid Disk partition
In this example, run the following command:
blkid /dev/vdb1
+[root@ecs-test-0001 ~]# blkid /dev/vdb1
+/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
In the command output, the TYPE value is ext4, indicating that /dev/vdb1's file system format is ext4.
- Run the following command to view the file system status:
ext*: e2fsck -n Disk partition
xfs: xfs_repair -n Disk partition
@@ -113,7 +117,7 @@ Warning! /dev/vdb1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/vdb1: clean, 11/6553600 files, 459544/26214144 blocks
- If the file system status is clean, the file system status is normal. Otherwise, rectify the faulty and then perform the capacity expansion.
+ If the file system status is clean, the file system is normal. Otherwise, rectify the faulty and then perform the capacity expansion.
Method 2: Check Partition Style and File System Format Using parted- Run the following command to view all the disks attached to the server:
lsblk
@@ -125,6 +129,8 @@ vdb 253:16 0 150G 0 disk
└─vdb1 253:17 0 100G 0 part /mnt/sdc
In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, /dev/vdb has 150 GiB, and /dev/vdb1 has 100 GiB.
+
- Run the following command and enter p to view the disk partition style:
parted Disk
For example, run the following command to view /dev/vdb's partition style:
parted /dev/vdb
@@ -140,17 +146,17 @@ Warning: Not all of the space available to /dev/vdb appears to be used, you can
blocks) or continue with the current setting?
Fix/Ignore? Fix
Model: Virtio Block Device (virtblk)
-Disk /dev/vdb: 161GB
+Disk /dev/vdb: 161GiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
- 1 1049kB 107GB 107GB ext4 test
+ 1 1049kB 107GiB 107GiB ext4 test
(parted)
- In the command output, parameter Partition Table indicates the disk partition style. Value msdos indicates the MBR partition style, and value gpt indicates the GPT partition style. - If the following error information is displayed, enter Fix.
Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the
+Partition Table indicates the disk partition style. Partition Table: msdos means MBR, Partition Table: gpt means GPT, and Partition Table: loop means that the whole disk is partitioned. - If the following error information is displayed, enter Fix.
Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the
disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
The GPT partition table information is stored at the start of the disk. To reduce the risk of damage, a backup of the information is saved at the end of the disk. When you expand the disk capacity, the end of the disk changes accordingly. In this case, enter Fix to move the backup file of the information to new disk end.
- If the following warning information is displayed, enter Fix.
Warning: Not all of the space available to /dev/vdb appears to be used, you can fix the GPT to use all of the space (an extra 104857600
diff --git a/docs/evs/umn/evs_01_0036.html b/docs/evs/umn/evs_01_0036.html
index 8fa877d8..b9f96fd9 100644
--- a/docs/evs/umn/evs_01_0036.html
+++ b/docs/evs/umn/evs_01_0036.html
@@ -1,23 +1,41 @@
Attaching a Non-Shared Disk
-ScenariosIndependently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the data disks to servers for use.
- A system disk must be created during a server creation and is automatically attached. In the disk list, the function of such disks is displayed as System disk, and the status is displayed as In-use. After a system disk is detached from a server, the disk function changes to Bootable disk, and the status changes to Available. Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.
+ ScenariosSeparately created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the data disks to servers for use.
+ A system disk must be created together with an ECS and is automatically attached. In the disk list, the function of such disks is displayed as System disk, and the status is displayed as In-use. After a system disk is detached from an ECS, the disk function changes to Bootable disk, and the status changes to Available. Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the disk function selected. For details, see Attaching an Existing System Disk.
- This section describes how to attach a non-shared disk. A non-shared disk can be attached to one server only.
+ This section describes how to attach a non-shared disk.
- ConstraintsCloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.
+ Prerequisites- The non-shared disk status is Available.
+
+ Constraints- Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.
- A non-shared disk can be attached to one server only.
- The disk and the server must be in the same region and AZ.
- A shared disk can be attached only when the servers' statuses are Running or Stopped.
- A frozen disk cannot be attached.
Attaching the Disk on the EVS Console- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Storage, click Elastic Volume Service.
The disk list page is displayed.
- - Locate the target disk in the list and click Attach.
The Attach Disk dialog box is displayed. Figure 1 Attach Disk dialog box
+ - Locate the target disk in the list and click Attach.
The Attach Disk dialog box is displayed. Figure 1 Attach Disk dialog box
- Select the server and then select a device name from the drop-down list. Ensure that the disk and server are in the same AZ.
- Click OK to return to the disk list page. The status of the disk is Attaching, indicating that the disk is being attached to the server. When the disk status changes to In-use, the disk is successfully attached.
- Initialize the disk.
After the disk has been attached to a server, the disk can be used only after you have initialized it. For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
+ - Select the server and then select the disk function from the drop-down list. Ensure that the disk and server are in the same AZ.
One device name can be used for one disk only. For how to obtain the disk name in the OS, see section "How Do I Obtain My Disk Name in the ECS OS Using the Device Identifier Provided on the Console?" in the Elastic Cloud Server User Guide.
+ - Click OK to return to the disk list page.
The status of the disk is Attaching, indicating that the disk is being attached to the server. When the disk status changes to In-use, the disk is successfully attached.
+ - Initialize the disk.
After the disk has been attached to a server, the disk can be used only after you have initialized it. For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.
Attaching the Disk on the ECS Console- Log in to the management console.
- Click
 in the upper left corner and select your region and project. - Under Computing, choose Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID for search.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
+ - Click the Disks tab. Then, click Attach Disk.
The Attach Disk dialog box is displayed.
+Figure 2 Attach Disk
+ - Select the target disk and specify it as the system disk or a data disk.
- If no disks are available, click Create Disk in the lower part of the list.
- For the restrictions on attaching disks, see FAQ "What Are the Requirements for Attaching an EVS Disk to an ECS?" in the Elastic Cloud Server User Guide.
- The device names for the local disks and EVS disks attached to a disk-intensive ECS comply with the following rules:
- System disk: sda or vda
- Local disk: the device name following sda or vda in alphabetical order
- EVS disk: the device name in alphabetical order following those used by local disks
+
+
+ - Click OK.
After the disk is attached, you can view the information about it on the Disks tab.
+Figure 3 Viewing the newly attached disk
+
+
diff --git a/docs/evs/umn/evs_01_0037.html b/docs/evs/umn/evs_01_0037.html
index b8078638..f2fbb14d 100644
--- a/docs/evs/umn/evs_01_0037.html
+++ b/docs/evs/umn/evs_01_0037.html
@@ -1,23 +1,41 @@
Attaching a Shared Disk
- ScenariosIndependently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the data disks to servers for use.
- This section describes how to attach a shared disk.
+ ScenariosSeparately created shared EVS disks are data disks. In the disk list, the function of such a disk is displayed as Data disk, and the status is displayed as Available. In this case, you need to attach the shared data disk to servers for use.
- Constraints- A shared disk can be attached to a maximum of 16 servers. These servers and the shared disk must be in the same AZ within a region.
If you simply attach a shared disk to multiple servers, files cannot be shared among them. Because there are no mutually agreed data read/write rules among servers, read and write operations from them may interfere with each other, or unpredictable errors may occur. To share files between servers, set up a shared file system or a clustered management system first.
+ Prerequisites- The shared disk status is In-use or Available.
+
+ Constraints If you simply attach a shared disk to multiple servers, files cannot be shared among them. Because there are no mutually agreed data read/write rules among servers, read and write operations from them may interfere with each other, or unpredictable errors may occur. To share files between servers, set up a shared file system or a clustered management system first.
- - If a shared disk is in the In-use state, ensure that the maximum number of servers that the disk can be attached to has not been reached.
- All the servers attached with a shared disk must run either Windows or Linux.
For example, if you attach a shared disk to multiple Windows servers and then detach it from these servers, the shared disk cannot be attached to Linux servers later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.
+- A shared disk can be attached to a maximum of 16 servers. These servers and the shared disk must be in the same AZ within a region.
- A shared, In-use disk can be attached to other servers only when the maximum number of servers that the disk can be attached to has not been reached.
- All the servers attached with a shared disk must run either Windows or Linux.
For example, if you attach a shared disk to multiple Windows servers and then detach it from these servers, the shared disk cannot be attached to Linux servers later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.
-- A shared disk can only be used as a data disk. It cannot be used as a system disk.
- Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.
+- A shared disk can only be used as a data disk. It cannot be used as a system disk.
- Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.
- A shared disk can be attached only when the servers' statuses are Running or Stopped.
- A frozen disk cannot be attached.
Attaching the Disk on the EVS Console- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Storage, click Elastic Volume Service.
The disk list page is displayed.
- - Locate the target disk in the list and click Attach.
The Attach Disk dialog box is displayed.
-Shared disks support batch attachment so that you can attach a shared disk to multiple servers. The left area in the Attach Disk dialog box shows the server list. After you select the target servers, the selected servers will be displayed in the right area. Figure 1 Attach Disk
+ - Locate the target disk in the list and click Attach.
The Attach Disk dialog box is displayed.
+Shared disks support batch attachment, so you can attach a shared disk to multiple servers. In the Attach Disk dialog box, the left area shows the server list. After you select the target servers, they will be displayed in the right area. Figure 1 Attach Disk
- Select the target servers and then select a device name from the drop-down list for each server you selected. Ensure that the disk and servers are in the same AZ.
- Click OK to return to the disk list page. The status of the disk is Attaching, indicating that the disk is being attached to the servers. When the disk status changes to In-use, the disk is successfully attached.
+ - Select the target servers you want to attach the shared disk. Ensure that the disk and servers are in the same AZ. After you select the servers, Data disk is automatically entered as the disk function for each server.
+
- Click OK to return to the disk list page.
The status of the disk is Attaching, indicating that the disk is being attached to the servers. When the disk status changes to In-use, the disk is successfully attached.
+
+ Attaching the Disk on the ECS Console- Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - Under Compute, click Elastic Cloud Server.
- In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID for search.
- Click the name of the target ECS.
The page providing details about the ECS is displayed.
+ - Click the Disks tab. Then, click Attach Disk.
The Attach Disk page is displayed.
+ - Select the target disk and specify it as the system disk or a data disk.
- For Xen ECSs, you can specify a specific device name, such as /dev/sdb.
- For KVM ECSs, you can specify the disk as the system disk or a data disk but cannot specify a specific device name.
+
|
