How to Increase vIDM appliance disk space
Article ID: 319356
Updated On:
Products
Issue/Introduction
Symptoms:
After a series of upgrades, the VMware Identity Manager (vIDM) appliances may not have the correct disk size for the updated version.
Resolution
What is generally observed is when the vIDM appliance has been updated several times, it still features the disk layout from the initial non-Photon installation:
The Photon versions features disk space pictured below:
To increase the disk size, please take the following steps:
Within vCenter, extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB (if Hard disk 4is present, it can be ignored).
NOTE: You cannot change the Hard Disk size if there are current snapshots. Take snapshots after the next step.
Take a snapshot of the VM.
Login as "root" to your appliance let Linux rescan for the disk changes:
echo 1 > /sys/class/block/sda/device/rescan
echo 1 > /sys/class/block/sdb/device/rescan
echo 1 > /sys/class/block/sdc/device/rescan
Verify with fdisk -l
Kindly select the options below depending on if we are extending the root, SDB or SDC
To Extend Data Partition - SDB & SDC:
Now you can extend the root partition by following steps below:
This step is applicable only for the root partition
cfdisk /dev/sda
1. Using arrow keys select /dev/sda4,
2. Using tab key Or shift tab select [ Resize ] then enter
3. Enter the free size available
- For Example we selected 2M in the screenshot below:
4. Using tab key select [ Write ]
5. type "yes"
6. Press tab to [ Quit ]
Next, you must resize the file system with "resize2fs" to use the new space:
[before resize2fs]
df -h | grep "sda4"
/dev/sda4 8.8G 3.9G 4.5G 47% /
[run resize2fs]
resize2fs /dev/sda4
[after resize2fs]
df -h | grep "sda4"
/dev/sda4 12G 3.9G 7.3G 35% /
Extend data partition - sdb & sdc:
To resize the two data partitions which are LVMs and the steps are different here versus root partition:
Use "pvresize" to let LVM know that the physical disk size has changed:
[before pvresize]
pvdisplay /dev/sdc /dev/sdb
--- Physical volume ---
PV Name /dev/sdc
VG Name tomcat_vg
PV Size 10.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID xxxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
--- Physical volume ---
PV Name /dev/sdb
VG Name db_vg
PV Size 10.00 GiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
[run pvresize]
pvresize /dev/sdb /dev/sdc
[after pvresize]
pvdisplay /dev/sdc /dev/sdb
--- Physical volume ---
PV Name /dev/sdc
VG Name tomcat_vg
PV Size <20.00 GiB / not usable 0
Allocatable yes
PE Size 4.00 MiB
Total PE 5119
Free PE 2560
Allocated PE 2559
PV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
--- Physical volume ---
PV Name /dev/sdb
VG Name db_vg
PV Size <20.00 GiB / not usable 0
Allocatable yes
PE Size 4.00 MiB
Total PE 5119
Free PE 2560
Allocated PE 2559
PV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxxExtend the logical volumes with "lvextend" to use the new space:
[before lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
--- Logical volume ---
LV Path /dev/tomcat_vg/horizon
LV Name horizon
VG Name tomcat_vg
LV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
LV Write Access read/write
LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:24 +0000
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 2559
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/db_vg/db
LV Name db
VG Name db_vg
LV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
LV Write Access read/write
LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:23 +0000
LV Status available
# open 1
LV Size <10.00 GiB
Current LE 2559
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
[run lvextend]
lvextend -l +100%FREE /dev/tomcat_vg/horizon
lvextend -l +100%FREE /dev/db_vg/db
[after lvextend]
lvdisplay /dev/tomcat_vg/horizon /dev/db_vg/db
--- Logical volume ---
LV Path /dev/tomcat_vg/horizon
LV Name horizon
VG Name tomcat_vg
LV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
LV Write Access read/write
LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:24 +0000
LV Status available
# open 1
LV Size <20.00 GiB
Current LE 5119
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/db_vg/db
LV Name db
VG Name db_vg
LV UUID xxxxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxxxx
LV Write Access read/write
LV Creation host, time sc-xxx-xxx-xxx, 2019-09-12 15:55:23 +0000
LV Status available
# open 1
LV Size <20.00 GiB
Current LE 5119
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
Finally, use "resize2fs" to extend the file system on the two LVs:
[before resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db 9.8G 1014M 8.3G 11% /db
/dev/mapper/tomcat_vg-horizon 9.8G 7.1G 2.2G 78% /opt/vmware/horizon
[run resize2fs]
resize2fs /dev/tomcat_vg/horizon
resize2fs /dev/db_vg/db
[after resize2fs]
df -h | grep "mapper"
/dev/mapper/db_vg-db 20G 1019M 18G 6% /db
/dev/mapper/tomcat_vg-horizon 20G 7.2G 12G 39% /opt/vmware/horizonFeedback
