Page Comparison

...

The process to increase the disk space allocated to DPOD's Store entails the two stages detailed below:

• Increasing the data disk and file system.
• Updating the application Store configuration fileIncrease Data Disk.
• Update Configuration File

Anchor
Increase Data Disk Increase Data Disk

Increase the Data Disk and File System

...

Select the correct OS level configuration procedure below, based on whether you selected to extend or add a disk.

• Extend existing configure extended disk
• Add configure new Diskdisk

Virtual appliance

With a virtual deployment, there are two options available for increasing DPOD's Store disk space:

• Extend the existing data hard driveExistinf Disk
• Add new data hard driveNew Disk

Anchor
Extend Existinf Disk Extend Existinf Disk

Extend

...

the existing Virtual Disk

Use the VMware 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 the DPOD virtual machine.
   
   

...

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

   Code Block
   df -h /data

   The system output should resemble the following:
   

2. Verify the new disk size:

   Code Block
   fdisk -l |grep /dev/sdc

   The system output should resemble the following:

   

3. 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 2. 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 created partition (Remember: if this is a subsequent disk extension - the number will be 3 or higher)
   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

       The system output should resemble the following (note the new sdcX added)
       

   12. Stop the application by running app-util.sh and selecting option 2 (stop all)

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

       
       

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

       Code Block
       pvcreate /dev/sdc2

       
       

   14.  Extend the LVM Volume Group (VG):

       Code Block
       vgextend vg_data /dev/sdc2

       
       

   15. Extend the LVM Logical Volume (LV):

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

       
       

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

       Code Block
       cat /etc/fstab |grep /data

       The system output should resemble the following:
       

   17.  Resize the file system. Select the correct command below for your file system type:

       Code Block
       title ext4
       resize2fs /dev/vg_data/lv_data

       
       

       Code Block
       title xfs
       xfs_growfs /dev/vg_data/lv_data

       The system output should resemble the following:
       

   18. To display the new size of the /data mount point:

       Code Block
       df -h /data

       
       

Anchor
Add New Disk Add New Disk

Add new virtual disk

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

1. Stop the DPOD virtual machine.
2. Select Edit virtual machine settings
3. Select Add > Hard Drive
4. Ensure to configure the new hard drive as Thick Provision Eager Zeroed
5.  Wait for the increase process to finish.
6. Start the DPOD virtual machine
   
   
   

Anchor
configure new disk configure new disk

Configure

...

the new disk at the OS Level

Display

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

/ data

2. :

   Code Block
   df -h /data

   The system output should resemble the following:
   Image Modified

...

1. Verify the new disk size:

   Code Block
   fdisk -l |grep /dev/sdd

   The system output should resemble the following:
   Image Modified

2. Create a new partition

...

1. with the new size:

   Code Block
   fdisk /dev/sdd

   
   

   1. Press p to print the partition table and

...

1. 1. ensure there are no existing partitions. 
      Image Modified
   2. Press n to create a new primary partition.
   3. Press p for primary.
   4. Press 1 for the partition number
   5. Press Enter

...

1. 1. twice
      Image Modified
   2. Press t to change the system's partition ID.
   3. Type 8e to change the Hex Code of the partition for Linux LVM.
   4. Press w to write the changes to the partition table.
      Image Modified

   5. Reboot the system:

      Code Block
      reboot

...

1. 1. 
      

   2. When the system is back up,

...

1. 1. ensure the new partition is created:

      Code Block
      fdisk -l |grep /dev/sdd

       The system output should resemble  the following:
      Image Modified

...

1. 1. Stop the application

...

1. 1. by running app-util.sh

...

1. 1.  and selecting option 2 (stop all)

...

1. 1. Create a new LVM

...

1. 1. Physical Volume (PV):

      Code Block
      pvcreate /dev/sdd1

...

1. 1. 
      

   2. Extend the LVM

...

1. 1. Volume Group (VG):

      Code Block
      vgextend vg_data /dev/sdd1

...

1. 1. 
      

   2.  Extend the LVM logical volume (LV): 

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

...

1. 1. 
      

   2.  Identify the /data file system

...

1. 1. type (for CentOS 7.2 based

...

1. 1. appliances the type is xfs): 

      Code Block
      cat /etc/fstab |grep /data

       The system output should resemble the following:
      Image Modified
      

...

1. 1. 
      

   2.  Resize the file system

...

1. 1. . Select the correct command below for your file system type:

      Code Block
      title ext4

...

1. 1. resize2fs /dev/vg_data/lv_data

      
      

      Code Block
      title xfs

...

1. 1. xfs_growfs /dev/vg_data/lv_data

      The system output should resemble the following:
      Image Modified
      

...

1. 1. 
      

   2. To display the new

...

1. 1. size of

...

1. 1. the /data mount point:

      Code Block
      df -h /data

      The system output should resemble the following:
      Image Modified

 

Anchor
Update Configuration File Update Configuration File

Update the Store Configuration File

Update Starting with v1.0.4, DPOD is shipped with a script that performs all the necessary steps to update the Store configuration file :

...

.

You may use this script by running:

 /app/scripts/update_store_allocation.sh  

...

...

When the script has completed, restart the application

...

by running app-util.sh

...

 and selecting option 1 (start all)