Instruction Manual for Capacity Expansion/Storage Specification Change of Public Cloud Hard Disk (EBS) within the Effective Range

1. Background

In a public cloud environment, the cloud hard disk directly connected to the cloud host stores a certain database data. With the accumulation of data, there are more than 1 billion pieces of data. The cloud hard disk needs to be expanded urgently. However, the cloud hard disk has not opened the lvm volume in the previous planning, and the current storage capacity The EBS capacity limit has not been reached, and the maximum can reach 32T, so it is decided to use the EBS specification change method to realize the expansion of the host storage;

Two, attention:

1) The partition needs to be rebuilt during the process, that is, delete the partition and create a new one

First of all, in the process of managing the partition table with the fdisk command, deleting the partition will not delete the actual data, which can be understood as the repair process after the partition is damaged or lost. In fact, Fdisk just rewrites the main boot sector of the hard disk (0 side 0 track 1 sector) is to delete the original partition table information of the hard disk, and the data of any partition in the hard disk has not been changed. You can even follow the mistakenly deleted data recovery method of "partition table error" to restore the partition and read back the data again, but it should be noted that it is only limited to after the partition has been deleted or rebuilt; if the partition has been formatted with the Format command, you need to restore the partition After that, restore the partition data. Therefore, pay attention to prevent process data from being written during operation.

2) Partition table refresh
insert image description here
3) Disk review

A disk device is composed of a large number of sectors, and the capacity of a sector is 512 bytes. The first sector of the disk is the most important, recording the master boot record and partition table information. MBR stores boot management programs (GRUB, LILO, NTLOARDER, etc.) and partition table records. As far as the first sector is concerned, the master boot information record needs to occupy 466 bytes, the partition table occupies 64 bytes, and the terminator occupies 2 bytes; each record of a partition information in the partition table requires

Guess you like

Origin blog.csdn.net/ximenjianxue/article/details/130687489