Updated on 2024-03-12 GMT+08:00

Extending Partitions and File Systems for Data Disks (Linux)

Scenarios

After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

In Linux, you must allocate the additional space to an existing partition or a new partition.

This section uses CentOS 7.4 64bit as the sample OS to describe how to extend an MBR or GPT partition. The method for allocating the additional space varies with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents.

Performing the expansion operations with caution. Incorrect operations may lead to data loss or exceptions. So you are advised to back up the disk data using CBR or snapshots before expansion. For details about using CBR, see Managing EVS Backups. For details about using snapshots, see Creating a Snapshot (OBT).

Prerequisites

Constraints

  • The additional space of a data disk cannot be added to the root partition. To extend the root partition, expand the system disk instead.
  • The additional space can only be added to the last partition of the disk.

Extending an Existing MBR or GPT Partition

Originally, data disk /dev/vdb has 100 GiB and one partition (/dev/vdb1), and then 50 GiB is added to the disk. The following procedure shows you how to add this 50 GiB to the existing MBR or GPT partition (/dev/vdb1).

  1. Run the growpart command to check whether growpart has been installed.

    If the tool usage instructions are returned, the tool has been installed, and you do not need to install it again. Skip step 2.

  2. Run the following command to install the growpart tool:

    yum install cloud-utils-growpart

  3. Run the following command to install the gdisk software package:

    yum install gdisk

    The following information is displayed:

    Is this ok [y/d/N]: 

    Enter Y and press Enter to complete the installation.

  4. Run the following command to view the disk partition information:

    fdisk -l

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
    
    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
    Disk label type: dos
    Disk identifier: 0x000bcb4e
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/vda1   *        2048    83886079    41942016   83  Linux
    
    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
    Disk label type: dos
    Disk identifier: 0x38717fc1
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/vdb1            2048   209715199   104856576   83  Linux

  5. Run the following command to view the size and file system type of the /dev/vdb1 partition:

    df -TH

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
    Filesystem     Type      Size  Used Avail Use% Mounted on
    devtmpfs       devtmpfs  509M     0  509M   0% /dev
    tmpfs          tmpfs     520M     0  520M   0% /dev/shm
    tmpfs          tmpfs     520M  7.1M  513M   2% /run
    tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
    /dev/vda1      ext4       43G  2.3G   38G   6% /
    tmpfs          tmpfs     104M     0  104M   0% /run/user/0
    /dev/vdb1      ext4      106G   63M  101G   1% /mnt/sdc

    In the command output, the Type column shows the file system type, the Size column shows the total partition size, and the Avail column shows the partition's available space. In this example, the file system type of the /dev/vdb1 partition is ext4, the total partition size is 106 GiB, and the partition's available space is 101 GiB.

  6. Run the following command to extend the partition using growpart:

    growpart Data disk Partition number

    In this example, run the following command:

    growpart /dev/vdb 1

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# growpart /dev/vdb 1
    CHANGED: partition=1 start=2048 old: size=209713152 end=209715200 new: size=314570719,end=314572767
    • If information similar to the following is displayed:
      no tools available to resize disk with 'gpt'
      FAILED: failed to get a resizer for id ''

      Install the gdisk software package according to 3.

    • If information similar to the following is displayed:
      growpart /dev/vda 1 unexpected output in sfdisk --version [sfdisk is from util-linux 2.23.2]

      Check that the system character set (language environment) is en_US.UTF-8.

  7. Extend the partition file system based on the file system type obtained in 5. The commands vary depending on file system types.

    • For the ext* file system, run the following command:

      resize2fs Disk partition

      In this example, run the following command:

      resize2fs /dev/vdb1

      Information similar to the following is displayed:
      [root@ecs-test-0001 ~]# resize2fs /dev/vdb1
      resize2fs 1.42.9 (28-Dec-2013)
      Filesystem at /dev/vdb1 is mounted on /mnt/sdc; on-line resizing required
      old_desc_blocks = 13, new_desc_blocks = 19
      The filesystem on /dev/vdb1 is now 39321339 blocks long.

      If the error message "open: No such file or directory while opening /dev/vdb1" is returned, an incorrect partition is specified. Run df -TH to view the disk partitions.

    • For the xfs file system, run the following command:

      sudo xfs_growfs Mount point

      In this example, run the following command:

      sudo xfs_growfs /mnt/sdc

      Information similar to the following is displayed:

      [root@ecs-test-0001 ~]# sudo xfs_growfs /mnt/sdc
      meta-data=/dev/vdb1              isize=512    agcount=4, agsize=6553536 blks
               =                       sectsz=512   attr=2, projid32bit=1
               =                       crc=1        finobt=0 spinodes=0
      data     =                       bsize=4096   blocks=26214144, imaxpct=25
               =                       sunit=0      swidth=0 blks
      naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
      log      =internal               bsize=4096   blocks=12799, version=2
               =                       sectsz=512   sunit=0 blks, lazy-count=1
      realtime =none                   extsz=4096   blocks=0, rtextents=0
      data blocks changed from 26214144 to 39321339

      In the example command, /mnt/sdc is the mount point on which /dev/vdb1 is mounted. Specify the mount point based on your site requirements.

  8. Run the following command to view the new capacity of the /dev/vdb1 partition:

    df -TH

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# df -TH
    Filesystem     Type      Size  Used Avail Use% Mounted on
    devtmpfs       devtmpfs  509M     0  509M   0% /dev
    tmpfs          tmpfs     520M     0  520M   0% /dev/shm
    tmpfs          tmpfs     520M  7.1M  513M   2% /run
    tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
    /dev/vda1      ext4       43G  2.3G   38G   6% /
    tmpfs          tmpfs     104M     0  104M   0% /run/user/0
    /dev/vdb1      ext4      156G   63M  151G   1% /mnt/sdc

Creating a New MBR Partition

Originally, data disk /dev/vdb has 100 GiB and one partition (/dev/vdb1), and then 50 GiB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/vdb2 with this 50 GiB.

  1. Run the following command to view the disk partition information:

    fdisk -l

    Information similar to the following is displayed:
    [root@ecs-test-0001 ~]# fdisk -l
    
    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
    Disk label type: dos
    Disk identifier: 0x000bcb4e
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/vda1   *        2048    83886079    41942016   83  Linux
    
    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
    Disk label type: dos
    Disk identifier: 0x38717fc1
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/vdb1            2048   209715199   104856576   83  Linux

  2. Run the following command to enter fdisk:

    fdisk 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.
    Be careful before using the write command.
    
    
    Command (m for help): 

  3. 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 (1 primary, 0 extended, 3 free)
       e   extended
    Select (default p):
    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 4 primary partitions, or 3 primary partitions plus 1 extended partition can be created. The extended partition must be divided into logical partitions before use.

    Disk partitions created using GPT are not categorized.

  4. 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
    Partition number (2-4, default 2):

    Partition number indicates the serial number of the primary partition. Because partition number 1 has been used, the value ranges from 2 to 4.

  5. Enter the serial number of the primary partition and press Enter. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

    Information similar to the following is displayed:
    Partition number (2-4, default 2): 2
    First sector (209715200-314572799, default 209715200):

    First sector indicates the start sector. The value ranges from 209715200 to 314572799, and the default value is 209715200.

  6. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

    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 (209715200-314572799, default 209715200):
    Using default value 209715200
    Last sector, +sectors or +size{K,M,G} (209715200-314572799, default 314572799):

    Last sector indicates the end sector. The value ranges from 209715200 to 314572799, and the default value is 314572799.

  7. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

    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} (209715200-314572799, default 314572799):
    Using default value 314572799
    Partition 2 of type Linux and of size 50 GiB is set
    
    Command (m for help): 

  8. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    Command (m for help): p
    
    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
    Disk label type: dos
    Disk identifier: 0x38717fc1
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/vdb1            2048   209715199   104856576   83  Linux
    /dev/vdb2       209715200   314572799    52428800   83  Linux
    
    Command (m for help): 

  9. 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.
    
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
    The kernel still uses the old table. The new table will be used at
    the next reboot or after you run partprobe(8) or kpartx(8)
    Syncing disks.

    In case that you want to discard the changes made before, you can exit fdisk by entering q.

  10. Run the following command to synchronize the new partition table to the OS:

    partprobe

  11. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition
    • Sample command of the ext* file system:

      mkfs -t ext4 /dev/vdb2

      Information similar to the following is displayed:
      [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb2
      mke2fs 1.42.9 (28-Dec-2013)
      Filesystem label=
      OS type: Linux
      Block size=4096 (log=2)
      Fragment size=4096 (log=2)
      Stride=0 blocks, Stripe width=0 blocks
      3276800 inodes, 13107200 blocks
      655360 blocks (5.00%) reserved for the super user
      First data block=0
      Maximum filesystem blocks=2162163712
      400 block groups
      32768 blocks per group, 32768 fragments per group
      8192 inodes per group
      Superblock backups stored on blocks:
              32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
              4096000, 7962624, 11239424
      
      Allocating group tables: done
      Writing inode tables: done
      Creating journal (32768 blocks): done
      Writing superblocks and filesystem accounting information: done
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/vdb2

      Information similar to the following is displayed:

      [root@ecs-test-0001 ~]# mkfs -t xfs /dev/vdb2 
      meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
               =                       sectsz=512    attr=2, projid32bit=1
               =                       crc=1         finobt=0, sparse=0
      data     =                       bsize=4096    blocks=13107200, imaxpct=25
               =                       sunit=0       swidth=0 blks
      naming   =version2               bsize=4096    ascii-ci=0 ftype=1
      log      =internal log           bsize=4096    blocks=6400, version=2
               =                       sectsz=512    sunit=0 blks, lazy-count=1
      realtime =none                   extsz=4096    blocks=0, rtextents=0

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

  12. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    mkdir Mount point

    In this example, run the following command to create the /mnt/test mount point:

    mkdir /mnt/test

  13. Run the following command to mount the new partition:

    mount Disk partition Mount point

    In this example, run the following command to mount the new partition /dev/vdb2 on /mnt/test:

    mount /dev/vdb2 /mnt/test

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

  14. Run the following command to view 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
    tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
    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
    /dev/vdb2      ext4       53G   55M   50G   1% /mnt/test

    If the server is restarted, the mounting will become invalid. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.

Creating a New GPT Partition

Originally, data disk /dev/vdb has 100 GiB and one partition (/dev/vdb1), and then 50 GiB is added to the disk. The following procedure shows you how to create a new GPT partition /dev/vdb2 with this 50 GiB.

  1. Run the following command to 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  150G  0 disk
    └─vdb1 253:17   0  100G  0 part /mnt/sdc

  2. Run the following command to enter parted:

    parted 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) 

  3. Enter unit s and press Enter to set the measurement unit of the disk to sector.
  4. Enter p and press Enter to view the disk partition information.

    Information similar to the following is displayed:
    (parted) unit s
    (parted) p
    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)?
    Fix/Ignore/Cancel? 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
    blocks) or continue with the current setting?
    Fix/Ignore? Fix
    Model: Virtio Block Device (virtblk)
    Disk /dev/vdb: 314572800s
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    Disk Flags:
    
    Number  Start  End         Size        File system  Name  Flags
     1      2048s  209713151s  209711104s  ext4         test
    
    (parted)
    In the command output, take note of the partition's end sector. In this example, the end sector of the /dev/vdb1 partition is 209713151s.
    • 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
      blocks) or continue with the current setting?
      Fix/Ignore? Fix

      Enter Fix as prompted. The system automatically sets the GPT partition style for the additional space.

  5. Run the following command and press Enter:

    mkpart Partition name Start sector End sector

    In this example, run the following command:

    mkpart data 209713152s 100%

    In this example, the additional space is used to create a new partition. In 4, the end sector of partition dev/vdb1 is 209713151s. Therefore, the start sector of the new partition dev/vdb2 is set to 209713152s and the end sector 100%. This start and end sectors are for reference only. You can plan the number of partitions and partition size based on service requirements.

    Information similar to the following is displayed:
    (parted) mkpart data 209713152s 100%
    (parted) 

    The maximum sector can be obtained in either of the following ways:

    • Query the disk's maximum end sector. For details, see 2 to 4.
    • Enter -1s or 100%, and the value displayed is the maximum end sector.

  6. Enter p and press Enter to view the new partition.

    Information similar to the following is displayed:
    (parted) p
    Model: Virtio Block Device (virtblk)
    Disk /dev/vdb: 314572800s
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    Disk Flags:
    
    Number  Start       End         Size        File system  Name  Flags
     1      2048s       209713151s  209711104s  ext4         test
     2      209713152s  314570751s  104857600s               data
    
    (parted) 

  7. Run the following command to set the file system format for the new partition:

    mkfs -t File system Disk partition

    • Sample command of the ext* file system:

      mkfs -t ext4 /dev/vdb2

      Information similar to the following is displayed:

      [root@ecs-test-0001 ~]# mkfs -t ext4 /dev/vdb2
      mke2fs 1.42.9 (28-Dec-2013)
      Filesystem label=
      OS type: Linux
      Block size=4096 (log=2)
      Fragment size=4096 (log=2)
      Stride=0 blocks, Stripe width=0 blocks
      3276800 inodes, 13107200 blocks
      655360 blocks (5.00%) reserved for the super user
      First data block=0
      Maximum filesystem blocks=2162163712
      400 block groups
      32768 blocks per group, 32768 fragments per group
      8192 inodes per group
      Superblock backups stored on blocks:
              32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
              4096000, 7962624, 11239424
      
      Allocating group tables: done
      Writing inode tables: done
      Creating journal (32768 blocks): done
      Writing superblocks and filesystem accounting information: done
    • Sample command of the xfs file system:

      mkfs -t xfs /dev/vdb2

      Information similar to the following is displayed:

      [root@ecs-test-0001 ~]# mkfs -t xfs /dev/vdb2 
      meta-data=/dev/vdb2              isize=512     agcount=4, agsize=3276800 blks
               =                       sectsz=512    attr=2, projid32bit=1
               =                       crc=1         finobt=0, sparse=0
      data     =                       bsize=4096    blocks=13107200, imaxpct=25
               =                       sunit=0       swidth=0 blks
      naming   =version2               bsize=4096    ascii-ci=0 ftype=1
      log      =internal log           bsize=4096    blocks=6400, version=2
               =                       sectsz=512    sunit=0 blks, lazy-count=1
      realtime =none                   extsz=4096    blocks=0, rtextents=0

    The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

  8. (Optional) Run the following command to create a mount point:

    Perform this step if you want to mount the partition on a new mount point.

    mkdir Mount point

    In this example, run the following command to create the /mnt/test mount point:

    mkdir /mnt/test

  9. Run the following command to mount the new partition:

    mount Disk partition Mount point

    In this example, run the following command to mount the new partition /dev/vdb2 on /mnt/test:

    mount /dev/vdb2 /mnt/test

    If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.

  10. Run the following command to view 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
    tmpfs          tmpfs     2.0G     0  2.0G   0% /dev/shm
    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
    /dev/vdb2      ext4       53G   55M   50G   1% /mnt/test

    If the server is restarted, the mounting will become invalid. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.

Configuring Automatic Mounting at System Start

The 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.

  1. 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"

    Carefully record the UUID, as you will need it for the following step.

  2. Open the fstab file using the vi editor.

    vi /etc/fstab

  3. Press i to enter editing mode.
  4. 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
    The preceding information is used for reference only. The line starting with UUID is the information added. Edit this line from left to right to match the following format:
    • UUID: The UUID obtained in 1.
    • Mount point: The directory on which the partition is mounted. You can query the mount point using df -TH.
    • Filesystem: The file system format of the partition. You can query the file system format using df -TH.
    • Mount option: The partition mount option. Usually, this parameter is set to defaults.
    • Dump: The Linux dump backup option.
      • 0: Linux dump backup is not used. Usually, dump backup is not used, and you can set this parameter to 0.
      • 1: Linux dump backup is used.
    • fsck: The fsck option, which means whether to use fsck to check the disk during startup.
      • 0: not use fsck.
      • If the mount point is the root partition (/), this parameter must be set to 1.

        If this parameter is set to 1 for the root partition, this parameter for other partitions must start with 2 because the system checks the partitions in the ascending order of the values.

  5. Press Esc, enter :wq, and press Enter.

    The system saves the configurations and exits the vi editor.

  6. Verify that the disk is auto-mounted at startup.

    1. Unmount the partition.

      umount Disk partition

      In this example, run the following command:

      umount /dev/vdb1

    2. Reload all the content in the /etc/fstab file.

      mount -a

    3. 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)