Updated on 2025-02-27 GMT+08:00

Step 1: Expand Disk Capacity

Scenarios

When your EVS disk capacity is insufficient, you can expand the disk capacity on the console to prevent any data loss that may be caused by insufficient storage space.

Prerequisites

Ensure that the disk meets the following conditions:

  • The status of a non-shared disk is In-use or Available.
  • The status of a shared disk is Available. If the status is In-use, detach the disk from all of its servers before expanding the capacity.
  • The disk has been backed up using CBR or snapshots. For details, see Backing Up EVS Disks and Managing EVS Snapshots respectively.

If the disk status is In-use, ensure that the server meets the following conditions:

  • The server status must be Running or Stopped.
  • The server OS must meet the requirements described in Related Operations.

    If the server OS does not meet the requirements, detach the disk and then expand the capacity. Otherwise, you may need to stop and start the server to see the additional space.

Notes and Constraints

  • Disk capacity can be expanded, but cannot be reduced.
  • The maximum capacity of a system disk is 1 TiB, and that of a data disk is 32 TiB. The minimum expansion increment is 1 GiB for both system disks and data disks.

Expanding the Capacity of a Single Disk

  1. Log in to the console.
  2. Choose an entry to expand the capacity.

    • To expand the disk on the ECS console (suitable for a disk that has been attached to an ECS):
      1. Choose Computing > Elastic Cloud Server to go to ECS list page.
      2. Click the name of the server where the desired disk is attached to go to the Summary page.
      3. Click the Disks tab, locate the disk you want to expand, and click Expand Capacity in the Operation column.
    • To expand the disk on the EVS console:
      1. Choose Storage > Elastic Volume Service to go to the EVS console.
      2. Locate the disk you want to expand and click Expand Capacity in the Operation column.

  3. On the Expand Capacity page, set New Capacity and click Next.
  4. On the Details page, check the disk configuration.

    • Click Submit to start the expansion.
    • Click Previous to change the settings, if required.

  5. In the displayed dialog box, click OK.
  6. In the disk list, view the capacity of the target disk.

    When the disk status changes from Expanding to In-use or Available, and the disk capacity increases, the expansion is successful.

    When a disk is in the Expanding state, you cannot modify the specifications of the ECS where the disk is attached.

  7. (Optional) If the disk status is Available, attach the disk to a server by referring to Attaching an EVS Disk. Skip this step if the disk status is In-use (attached to a server).
  8. After the disk has been expanded on the console, log in to the server and extend the partition and file system, because the previous steps only enlarge the disk space.

    The operations vary depending on the server OS.

Related Operations

Perform the following operations to check whether your server OS allows you to expand In-use disks:

  1. Check your server image. Certain public images and similar private images allow you to expand In-use disks. You do not need to stop and then start the servers after the expansion.

    To view such images, log in to the console, click in the navigation pane on the left, and choose Compute > Image Management Service. On the Public Images tab, view the images of the ECS system disk image type.

  2. If your server OS is not in the image list, check whether it is included in Table 1.

    If it is included in Table 1, you can expand capacity while the disk is in use and you do not need to stop and start the server after the expansion. Otherwise, you must detach the disk and then expand its capacity, or stop and start the server after the expansion.

    Table 1 OSs that support the capacity expansion of In-use disks

    OS

    Version

    CentOS 8

    8.0 64-bit or later

    CentOS 7

    7.2 64-bit or later

    CentOS 6

    6.5 64-bit or later

    Debian

    8.5.0 64-bit or later

    Fedora

    24 64-bit or later

    SUSE 12

    SUSE Linux Enterprise Server 12 64-bit or later

    SUSE 11

    SUSE Linux Enterprise Server 11 SP4 64-bit

    OpenSUSE

    42.1 64-bit or later

    Oracle Linux Server release 7

    7.2 64-bit or later

    Oracle Linux Server release 6

    6.7 64-bit or later

    Ubuntu Server

    14.04 64-bit or later

    Red Hat Enterprise Linux 7

    7.3 64bit

    Red Hat Enterprise Linux 6

    6.8 64bit

    EulerOS

    2.2 64-bit or later

    Windows Server 2016

    Windows Server 2016 R2 Enterprise 64-bit

    Windows Server 2012

    Windows Server 2012 R2 Standard 64-bit

    Windows Server 2008

    Windows Server 2008 R2 Enterprise 64-bit