...
AnchorExtend Existinf Disk Extend Existinf Disk
Extend The Existing Virtual Disk
Extend Existinf Disk | |
Extend Existinf Disk |
...
Verify the current size of mount point /data:
Code Block df -h /data
The system output should resemble the following:
Verify the new disk size:
Code Block fdisk -l |grep /dev/sdc
The system output should resemble the following:
Use fdisk to create a new partition for the new size:
Code Block fdisk /dev/sdc
and perform the following steps:
- 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) - Press n to create a new primary partition.
- Press p for primary.
- 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. - Press Enter twice
- Press t to change the system's partition ID.
- Press 2 to select the newly created partition (Remember: if this is a subsequent disk extension - the number will be 3 or higher)
- Type 8e to change the Hex Code of the partition for Linux LVM.
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)”Reboot the system:
Code Block reboot
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)
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
Create a new LVM Physical Volume (PV):
Code Block pvcreate /dev/sdc2
Extend the LVM Volume Group (VG):
Code Block vgextend vg_data /dev/sdc2
Extend the LVM Logical Volume (LV):
Code Block lvextend -l +100%FREE /dev/vg_data/lv_data
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:
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:
To display the new size of the /data mount point:
Code Block df -h /data
- Press p to print the partition table to identify the number of partitions:
...
- Stop the DPOD virtual machine.
- Select Edit virtual machine settings
- Select Add > Hard Drive
- Ensure to configure the new hard drive as Thick Provision Eager Zeroed
- Wait for the increase process to finish.
- Start the DPOD virtual machine
Anchor | ||||
---|---|---|---|---|
|
- Display
Verify the current size of the /data mount point
/ data :
Code Block df -h /data
The system output should resemble the following:
...
Verify the new disk size:
Code Block fdisk -l |grep /dev/sdd
The system output should resemble the following:
Create a new partition
...
with the new size:
Code Block fdisk /dev/sdd
- Press p to print the partition table and
...
- ensure there are no existing partitions.
- Press n to create a new primary partition.
- Press p for primary.
- Press 1 for the partition number
- Press Enter
- ensure there are no existing partitions.
...
- twice
- Press t to change the system's partition ID.
- Type 8e to change the Hex Code of the partition for Linux LVM.
- Press w to write the changes to the partition table.
Reboot the system:
Code Block reboot
- twice
...
When the system is back up,
...
ensure the new partition is created:
Code Block fdisk -l |grep /dev/sdd
The system output should resenble the following:
...
- Stop the application
...
- by running app-util.sh
...
- and selecting option 2 (stop all)
...
Create a new LVM
...
Physical Volume (PV):
Code Block pvcreate /dev/sdd1
...
Extend the LVM
...
Volume Group (VG):
Code Block vgextend vg_data /dev/sdd1
...
Extend the LVM logical volume (LV) :
Code Block lvextend -l +100%FREE /dev/vg_data/lv_data
...
Identify the /data file system
...
type (for CentOS 7.2 based
...
appliances the type is xfs):
Code Block cat /etc/fstab |grep /data
The system output should resemble the following:
...
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:
...
To display the new size of
...
the /data mount point:
Code Block df -h /data
The system output should resemble the following:
Anchor Update Configuration File Update Configuration File
Update the Store Configuration File
Update Configuration File | |
Update Configuration File |
Update Starting with v1.0.4.0, 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:
Code Block | ||||
---|---|---|---|---|
| ||||
/app/scripts/update_store_allocation.sh |
Info |
---|
The script is available on DPOD v1.0.4.0 and above. If you are using earlier version please contact DPOD support and the script will be provided. |
...
When the script has completed, restart the application
...
by running app-util.sh
...
and selecting option 1 (start all)