No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Insufficient Disk Space of the Management Node

Insufficient Disk Space of the Management Node

Prerequisite: The disk to be scaled out has been attached to the node.

Symptom

The following disk error information is displayed during the health check and inspection:

10.109.223.91:
Filesystem                  Size  Used Avail Use% Mounted on
devtmpfs                     16G  8.0K   16G   1% /dev
tmpfs                        16G   80K   16G   1% /dev/shm
tmpfs                        16G  1.6G   15G  11% /run
tmpfs                        16G     0   16G   0% /sys/fs/cgroup
/dev/xvda2                   36G   20G   15G  58% /
/dev/mapper/docker-vol_opt  138G  121G   11G  92% /opt

Possible Causes

The disk space is insufficient. The df -h command output displays that the value of Use% of the disk exceeds 90%.

Troubleshooting Method

  1. Log in to the abnormal node as the paas user. Run the following command and enter the password as prompted to switch to the root user:

    su - root

  2. Check the name of the new scale-out disk. (Prerequisite: The scale-out disk has been attached to the server.)

    fdisk -l

    The scale-out disk (/dev/mapper/docker-vol_opt) is displayed.

    Assume that the newly added disk is /dev/xvde.

  3. Create a physical volume (PV).

    pvcreate /dev/xvde

    In this command output, /dev/xvde is the newly added disk queried in 2.

  4. Check the size and name of the volume group (VG).

    vgdisplay

    In this command output, VG Name indicates the VG name, and VG Size indicates the VG size. If multiple disks are attached to a host, several VG names will be displayed. Select the VG used for scaling out to perform subsequent operations.

  5. Add the new disk to the original VG.

    vgextend vg_centos /dev/xvde

    In the preceding command output, vg_centos indicates the VG name queried in 4, and /dev/xvde indicates the PV created in 3.

    Run the vgdisplay command to check the VG again.

    If successfully is displayed in the command output, the command execution succeeds.

    In the preceding command output, 63999 indicates the number of idle PEs.

  6. Scale out a logical volume (LV).

    lvextend -l +63999 /dev/mapper/vg_centos-lv_root

    In the preceding command, /dev/mapper/vg_centos-lv_root is the name of scale-out Filesystem in the health check report.

    If successfully is displayed in the command output, the command execution succeeds.

  7. Check the scale-out result of the LV.

    lvs

  8. Adjust the file system size.

    resize2fs /dev/mapper/vg_centos-lv_root

    In the preceding command, /dev/mapper/vg_centos-lv_root is the name of scale-out Filesystem in the health check report.

    If "*** blocks long" is displayed in the command output, the command execution succeeds.

  9. Check the scale-out result.

    df -Th

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1185

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next