Page Comparison

...

• Increasing the data disk and file system.
• Updating the application Store configuration file
  
  

Extend the Data Disk

Virtual appliance

There are two strategies for increasing the disk space for the DPODs Store  

• Extend the existing data hard drive
• Add new data hard drive

Extend the existing virtual disk

Use the vSphere Client in order to edit the DPODs virtual machine

• • Stop DPOD virtual machine.
  • Press “Edit virtual machine settings”
  • Choose the 3rd hard drive (which is the data disk as described in DPODs installation procedure).
  • Increase the “Provisioned size” of the hard drive and press OK.
  • Wait for the increase process to finish.
  • Start DPOD virtual machine.

 Image Added

Use the vSphere Client in order to edit the DPODs virtual machine

• • Display the current size of mount point / data : df -h /data
    Image Added
    
    
  • Display the new disk size : fdisk -l |grep /dev/sdc
    Image Added
    
    
  • Create new partition for the new size :
    • fdisk /dev/sdc
    • Press p to print the partition table to identify the number of partitions.
      If this is the first disk extending there should be only sdc1. If this is the second time there should be sdc1 and sdc2.
      Image Added
      
      
    • Press n to create a new primary partition.
    • Press p for primary.
    • Press 2 for the partition number, depending on the output of the partition table print (if this is the second disk extending then the partition number will be 3 )
    • Press Enter two times.
      Image Added
      
      
    • Press t to change the system's partition ID.
    • Press 2 to select the newly creation partition.
    • Type 8e to change the Hex Code of the partition for Linux LVM.

    • Press w to write the changes to the partition table.
      Image Added
      
      

      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)”

      
      
      

    • Reboot the system : reboot
    • After the system is up, make sure you see the new partition : fdisk -l |grep /dev/sdc
      Image Added
      
      
    • stop the application using app-util.sh -> option 2 (stop all)
    • create new LVM physical volume (PV) : pvcreate /dev/sdc2
      if this is the second disk extending the device will be /dev/sdc3
    • extend the LVM volume group (VG) : vgextend vg_data /dev/sdc2
    • extend the LVM logical volume (LV) :
      lvextend -l +100%FREE /dev/vg_data/lv_data
    • identify the /data file system type (for CentOS 7.2 based appliance the type is xfs) : cat /etc/fstab |grep /data
      Image Added
      
      
    • resize the file system according to the file system type :
    • ext4 : resize2fs /dev/vg_data/lv_data
    • xfs : xfs_growfs /dev/vg_data/lv_data
      Image Added
      
      
    • Display the new  size of mount point / data : df -h /data
      Image Added