Versions Compared

Key

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

...

Info

The following procedure is applicable to All-in-One DPOD appliance mode installation only.

In non-appliance installations, the operating system and file system configuration is under the responsibility of the customer, so the following procedure can only be used as an example, since the actual existing file system configuration might not match the one created in the appliance mode installation.

For details about the Store space in a Cell environment, see Setup a Cell Environment.

...

DPOD's Big Data Store is located on a dedicated mount point. Occasionally, the disk space allocated for the Store needs to be increased. Reasons for that include an increase in TPS, or a requirement to retain history for longer periods of time. Follow the steps below to increase the Store space.

Note: It is possible to extend You may choose between extending the existing data disk (option 1), or add an adding additional disks (option 2).
Since DPOD uses fdisk utility supports disks up to 2TB each, in order to increase the Store space above 2TB, add additional disks (option 2) instead of extending a single for creating partitions in the data disk, it only supports extending the existing data disk (option 1) .
Choose the option below that is suitable for your environment and requirementsup to 2TB. However, additional disks (option 2) can be larger than 2TB.

Option 1: Extending the Existing Data Disk

...

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

    Code Block
    languagebash
    themeRDark
    df -h /data

    The system output should resemble the following:


  2. Verify the new disk size:

    Code Block
    languagebash
    themeRDark
    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
    languagebash
    themeRDark
    fdisk /dev/sdc


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


  4. Reboot the system:

    Code Block
    languagebash
    themeRDark
    reboot


  5. When the system is available again, ensure the new partition is available:

    Code Block
    languagebash
    themeRDark
    fdisk -l | grep /dev/sdc

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


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

  7. Create a new LVM Physical Volume (PV)Configure the new partition:

    Note

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


    Code Block
    languagebash
    themeRDark
     pvcreate /dev/sdc2

    Extend the LVM Volume Group (VG):

    Code Block
    languagebash
    themeRDark
    
    vgextend vg_data /dev/sdc2

    Extend the LVM Logical Volume (LV):

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


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

    Code Block
    languagebash
    themeRDark
    cat /etc/fstab | grep /data

    The system output should resemble the following:


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

    Code Block
    languagebash
    themeRDark
    titleFor ext4
    resize2fs /dev/vg_data/lv_data


    Code Block
    languagebash
    themeRDark
    titleFor xfs
    xfs_growfs /dev/vg_data/lv_data


    The system output should resemble the following:


  10. Display the new size of the /data mount point:

    Code Block
    languagebash
    themeRDark
    df -h /data


  11. Update the Store configuration file (see below).

...

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

    Code Block
    languagebash
    themeRDark
    df -h /data

    The system output should resemble the following:

  2. Verify Identify the new disk size:

    Code Block
    languagebash
    themeRDark
    fdisklsblk
    
    -l[ |Note: grep /dev/sdd

    The system output should resemble the following:
    Image Removed

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

    Code Block
    languagebash
    themeRDark
    fdisk /dev/sdd
  3. Press p to print the partition table and ensure there are no existing partitions. 
    Image Removed
  4. Press n to create a new primary partition.
  5. Press p for primary.
  6. Press 1 for the partition number
  7. Press Enter twice
    Image Removed
  8. Press t to change the system's partition ID.
  9. Type 8e to change the Hex Code of the partition for Linux LVM.
  10. Press w to write the changes to the partition table.
    Image Removed

    Reboot the system:

    Code Block
    languagebash
    themeRDark
    reboot

    When the system is available again, ensure the new partition is created:

    Code Block
    languagebash
    themeRDark
    fdisk -l | grep /dev/sdd
     The system output should resemble  the following:
    Image Removed
    Example output below is filtered to show only sdd disk information, but should include many more entries of sda, sdb and sdc disks ]
    
    NAME                    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    sdd                       8:32   0  200G  0 disk 


  11. Stop the application by running app-util.sh and selecting option 2 (stop all)
    Create a new LVM Physical Volume (PV):

  12. Execute the following commands. Replace the name of data disk if it is different in your environment.

    Code Block
    languagebash
    themeRDark
    pvcreate -ff /dev/sdd1

    Extend the LVM Volume Group (VG):

    Code Block
    languagebash
    themeRDark
    sdd
    vgextend vg_data /dev/sdd1

    Extend the LVM logical volume (LV):

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


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

    Code Block
    languagebash
    themeRDark
    cat /etc/fstab | grep /data

     The system output should resemble the following:



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

    Code Block
    languagebash
    themeRDark
    titleFor ext4
    resize2fs /dev/vg_data/lv_data


    Code Block
    languagebash
    themeRDark
    titleFor xfs
    xfs_growfs /dev/vg_data/lv_data


    The system output should resemble the following:


  15. Display the new size of the /data mount point:

    Code Block
    languagebash
    themeRDark
    df -h /data

    The system output should resemble the following:


  16. Update the Store configuration file (see below).

...