In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/03 Report--
How to expand the capacity of the system disk without changing the operating system image? In response to this problem, the editor summed up this article today, hoping to help more friends who want to solve this problem to find a more simple and feasible way.
Expansion system disk
With the development of your business, if you need to expand the capacity of the system disk, you can do so by replacing the system disk function. This article only describes how to expand the system disk capacity without replacing the operating system image.
Description
While expanding the system disk, you can also change the operating system. For specific operations, see changing the operating system.
Matters needing attention
Replacing the system disk is a high-risk operation, so be sure to read the following notes carefully before replacing the system disk.
Risk
There are the following risks in replacing the system disk:
Replacing the system disk requires stopping the instance, so it will disrupt your business.
After the replacement is completed, you need to redeploy the business operating environment in the new system disk, which may cause a long interruption to your business.
Replacing the system disk is to reassign a system disk to your instance, and the ID of the cloud disk will change, so snapshots created based on the old system disk cannot be used to roll back the new system disk.
Description
After you replace the system disk, the snapshots you create manually are not affected, and you can still use these snapshots to create custom mirrors. If you set the automatic snapshot policy for the old system disk and set the automatic snapshot to be released with the cloud disk, the automatic snapshot policy is no longer applicable to the new system disk, and the automatic snapshot of the old system disk is automatically deleted.
Restrictions and description
When replacing the system disk, you need to pay attention to the following information:
After replacing the system disk, your instance will be assigned a new system disk, the system disk ID will be updated, and the original system disk will be released.
You cannot change the cloud disk type of the system disk.
The minimum capacity of the expanded system disk is that before expansion, and the maximum capacity is 500 GiB. The capacity of the system disk cannot be reduced.
Windows 2003 does not support system disk expansion.
If your prepaid instance has been renewed and downconfigured, you cannot modify the system disk capacity before entering the next billing cycle.
The IP address and MAC address of the instance remain unchanged.
Before expanding the capacity of the system disk, it is recommended that you create a snapshot for the system disk. Note the following restrictions when creating a snapshot:
Avoid creating snapshots during peak hours of your business, so as not to affect your business. A 40-GiB snapshot takes about 40 minutes to create for the first time. So please set aside enough time. "also, creating a snapshot may degrade the block storage Iripple O performance (typically less than 10%), slowing down briefly."
When creating a snapshot of the system disk, make sure that there is enough space on the system disk, and it is recommended to reserve 1 GiB of space, otherwise the system may not start normally after the system disk is expanded and replaced.
To ensure that there is enough snapshot quota to complete the automatic snapshot policy for the new system disk, you can delete the old system disk snapshot that you do not need. For more information, see deleting Snapshots and automatic Snapshot policies.
Operation steps
If you want to expand the capacity of the system disk while retaining the contents of the original system disk, you must follow these steps to replace the system disk:
Log in to the ECS Management console.
In the left navigation bar, click the instance.
Select the region.
Find the instance that needs to expand the capacity of the system disk, and click the instance ID to enter the instance details page.
Follow these steps to create a snapshot of the system disk:
In the left navigation bar, click the disk for this instance.
Locate the system disk, and in the actions column, click create Snapshot.
Description
"for detailed operational restrictions or considerations for creating snapshots, see creating Snapshots."
Follow these steps to create a custom mirror using a system disk snapshot:
In the left navigation bar, click the snapshot of this instance to view the progress and status of the snapshot creation. When the progress is 100% and the status is displayed as successful, in the Action column, click create Custom Mirror.
Description
"for detailed operational restrictions or considerations for creating a custom mirror, see creating a Custom Mirror using Snapshots."
When changing the system disk, the image obtained in this way will appear in the drop-down list of custom images.
Go back to the instance list page, and in the left navigation bar, select Snapshot and Mirror > Mirror to view the creation progress and status of the custom image.
When the progress of creating a custom image is 100% and the status is available, in the left navigation bar, click the instance.
Find the instance of the action you want, and in the action column, select more > stop.
Description
If it is a postpaid VPC instance and you have enabled the no charge feature for downtime of postpaid instances, click OK in the pop-up box. In the stop instance dialog box, choose to stop and keep the instance and continue to charge. If the downtime free mode is used, the instance may not be started successfully after the system disk is replaced.
When the status of the instance is displayed as stopped, in the actions column, select more > replace the system disk.
In the pop-up dialog box, after carefully reading the notes for replacing the system disk, click OK to replace the system disk.
On the replace system disk page
Image type: select the custom image you just created from the custom image.
System disk: the capacity of the system disk is modified according to business requirements, and the maximum capacity can be expanded to 500 GiB. The minimum capacity that can be set during capacity expansion is related to the current capacity and image of the system disk, as shown in the following table.
Description
The cloud disk type of the system disk cannot be modified.
Security Settings:
If it is a Windows system, you can only use password authentication.
If your instance is an Linux O optimized instance and it is a Linux system, you can choose to use password authentication or SSH key pair authentication. You can set the login password or bind the SSH key pair.
Confirm the configuration fee: includes the price of the image and the price of the system disk. Please refer to the price page of cloud products for details.
Once confirmed, click OK to replace.
You can monitor the system status through the console, and it will take about 10 minutes to complete the operating system replacement. After completion, the instance will start automatically.
Subsequent operation
After replacing the system disk, you may need to do the following:
If the Linux system is mounted and the instance mounts the data disk automatically: after the system disk is replaced, the file system mount information in the original system disk is lost. You must write the new partition information in the / etc/fstab file of the new system disk and mount the file system, but you do not need to format and partition the data disk. The operation steps are as follows. For specific operation commands, please see Linux formatting and mounting the data disk:
(recommended) backup / etc/fstab.
Write new partition information to / etc/fstab.
View the new partition information in / etc/fstab.
Mount the file system.
Check the current cloud disk space and usage: run the command df-h.
After the mount operation is complete, you do not need to restart the instance to start using the new file system.
Set the automatic snapshot policy for the disk. The automatic snapshot policy is bound to the cloud disk ID. After the new system disk is replaced, the automatic snapshot policy applied on the old cloud disk automatically expires. You need to set the automatic snapshot policy for the new system disk.
After reading this article, have you learned how to expand the capacity of the system disk without changing the operating system image? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel. Thank you for reading.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.