Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
Extend Existinf Disk
Extend Existinf Disk
Extend The Existing Virtual Disk

Use the vSphere Client in order to edit the DPOD virtual machine
  1. Stop the DPOD virtual machine.
  2. Select Edit virtual machine settings
  3. Select the 3rd hard drive (which is the data disk, as described in the Hardware and Software Requirements page).
  4. Increase the Provisioned size of the hard drive and press OK.
  5. Wait for the increase process to finish.
  6. Start DPOD virtual machine.

...

  1. Verify the current size of mount point /data:

    Code Block
    df -h /data


  2. The system output should resemble the following:
  3. Verify the new disk size:

    Code Block
    fdisk -l |grep /dev/sdc


  4. The system output should resemble the following:

  5. Use fdisk to create a new partition for the new size:

    Code Block
    fdisk /dev/sdc

     and perform the following steps:

    1. Press p to print the partition table to identify the number of partitions:

      If this is the first time the disk is extended, you should only see sdc1. If this is a subsequent extension - you will see additional sdcX listed (e.g. sdc2 for the second extension)
    2. Press n to create a new primary partition.
    3. Press p for primary.
    4. When the system prompts for a partition number enter the next number depending on the output of the partition table print. If this is the first extension and you see only one row of output - enter 1. If this is the second disk extension then the partition number will be 3, and so on.
    5. Press Enter twice
    6. Press t to change the system's partition ID.
    7. Press 2 to select the newly creation partition.
    8. Type 8e to change the Hex Code of the partition for Linux LVM.
    9. Press w to write the changes to the partition table.



      Note

      the following warning is valid, the system reboot will fix the issue :
      “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)”


    10. Reboot the system:

      Code Block
      reboot

       

    11. When the system is back up, ensure the new partition is available:

      Code Block
      fdisk -l | grep /dev/sdc


    12. The system output should resemble the following (note the new sdcX added)
  6. stop
    1. Stop the application

  7. using
    1. by running app-util.sh

  8. ->
    1.  and selecting option 2 (stop all)

  9. create new LVM physical volume extend the LVM volume group
    1. Note

      If the new partition is not sdc2, substitute sdc2 for the right qualifier in all the following commands


    2. Create a new LVM Physical Volume (PV):

      Code Block
       pvcreate /dev/sdc2
  10. if this is the second disk extending the device will be /dev/sdc3

    1.  Extend the LVM Volume Group (VG):

      Code Block
      vgextend vg_data /dev/sdc2
  11. extend

    1. Extend the LVM

  12. logical volume
    1. Logical Volume (LV):

      Code Block
      lvextend -l +100%FREE /dev/vg_data/lv_data
  13. identify

    1.  Identify the /data file system type (for CentOS 7.2 based appliance the type is xfs):

      Code Block
      cat /etc/fstab |grep /data


    2. The system output should resemble the following:
      Image Modified
  14. resize
    1.  Resize the file

  15. system according to the
    1. systemץ Use the correct command for your file system type:

      Code Block
      titleext4
  16. :
    1. resize2fs /dev/vg_data/lv_data


      Code Block
      titlexfs
  17. :
    1. xfs_growfs /dev/vg_data/lv_data


    2. The system output should resemble the following:
      Image Modified
  18. Display
    1. To display the new
  19.  size
    1. size of the /data mount point
  20. / data
    1. :


      Code Block
      df -h /data

...


Anchor
Add New Disk
Add New Disk
Add new virtual disk

...