How to Increase vIDM appliance disk space
Article ID: 319356
Updated On:
Products
VMware Aria Suite
Issue/Introduction
- This Article provides instructions on how to increase the disk size of all VMware Identity Manager (vIDM) nodes.
- After a series of upgrades, the VMware Identity Manager (vIDM) appliances may not have the correct disk size for the updated version.
Environment
VMware Identity Manager 3.X
Resolution
- Important Note: Delete any existing snapshots before resizing the hard disk, as disk size cannot be changed with active snapshots. Take new snapshots only after extending the disk.
-
Since we are making disk changes and snapshot cannot be used as back up before modify the size of the disk. Broadcom recommends to back up the appliances either by taking a full offline clone with all nodes powered off, or use 3rd party back up utility.
- Run the below command on the appliance to identify the disk and associate SCSI ID.
df -h;lsscsi;lsblk - 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:
- Within vCenter, Shut down the Identity Manager virtual machine.
- Right-click the Identity Manager virtual machine and click Edit Settings.
- Extend Hard disk 1 to 60GB and Hard disk 2 and 3 to 20GB (if Hard disk 4 is present, it can be ignored).
- Please extend the disk based on the file system in question. it is not mandatory to extend all the hard disks.
Note: Take a snapshot of the VM as the hard disk size has been extended.
- Please extend the disk based on the file system in question. it is not mandatory to extend all the hard disks.
- Putty into the node as "root" and run the below command to 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
Click the appropriate hyperlink below based on whether you are extending Root, SDB, or SDC.
To Extend Data Partition - SDB:
To Extend Data Partition - SDC:
Extend the root partition by following steps below:
1. Invoke partitioning tool (menu-driven interface) by running the below command.
# cfdisk /dev/sdaNote: This step is applicable only for the root partition:
2. Using arrow keys select
/dev/sda43. Using tab key Or shift tab select [ Resize ] then enter
4. Enter the New Disk Size to Expand the Root Partition- Note: start by checking how much free space is available on /dev/sda. Next, make sure the new disk size is larger than the current root partition. For example, if you plan to add additional 10 GB, the new total size should be the ( current root partition size + 10 GB ) which should be available in free space.
5. Using tab key select [ Write ]
6. type "yes"
7. Press tab to [ Quit ]
8. 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% /9. Run
'df -h'command to verify the allocated space.To resize the two data partitions which are LVMs and the steps are different here versus root partition:
Extend the sdb data partition:
1. Use "pvresize" to let LVM know that the physical disk size has changed:
[before pvresize] # pvdisplay /dev/sdb --- 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 ######-####-####-####-####-####-###### [run pvresize] # pvresize /dev/sdb [after pvresize] # pvdisplay /dev/sdb --- 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 ######-####-####-####-####-####-######2. Extend the logical volumes with "lvextend" to use the new space:[before lvextend] # lvdisplay /dev/db_vg/db --- Logical volume --- LV Path /dev/db_vg/db LV Name db VG Name db_vg LV UUID ######-####-####-####-####-####-###### LV Write Access read/write LV Creation host, time sc-###-###-###, 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/db_vg/db [after lvextend] # lvdisplay /dev/db_vg/db --- Logical volume --- LV Path /dev/db_vg/db LV Name db VG Name db_vg LV UUID ######-####-####-####-####-####-###### LV Write Access read/write LV Creation host, time sc-###-###-###, 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:03. 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 [run resize2fs] # resize2fs /dev/db_vg/db [after resize2fs] # df -h | grep "mapper" /dev/mapper/db_vg-db 20G 1019M 18G 6% /db4. Run
'df -h'command to verify the allocated space.
1. Use "pvresize" to let LVM know that the physical disk size has changed:[before pvresize] # pvdisplay /dev/sdc --- 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 ######-####-####-####-####-####-###### [run pvresize] # pvresize /dev/sdc [after pvresize] # pvdisplay /dev/sdc --- 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 ######-####-####-####-####-####-######2. Extend the logical volumes with "lvextend" to use the new space:[before lvextend] # lvdisplay /dev/tomcat_vg/horizon --- Logical volume --- LV Path /dev/tomcat_vg/horizon LV Name horizon VG Name tomcat_vg LV UUID ######-####-####-####-####-####-###### LV Write Access read/write LV Creation host, time sc-####-####-####, 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 [run lvextend] # lvextend -l +100%FREE /dev/tomcat_vg/horizon [after lvextend] # lvdisplay /dev/tomcat_vg/horizon --- Logical volume --- LV Path /dev/tomcat_vg/horizon LV Name horizon VG Name tomcat_vg LV UUID ######-####-####-####-####-####-###### LV Write Access read/write LV Creation host, time sc-####-####-####, 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:13. Finally, use "resize2fs" to extend the file system on the two LVs:[before resize2fs] # df -h | grep "mapper" /dev/mapper/tomcat_vg-horizon 9.8G 7.1G 2.2G 78% /opt/vmware/horizon [run resize2fs] # resize2fs /dev/tomcat_vg/horizon [after resize2fs] # df -h | grep "mapper" /dev/mapper/tomcat_vg-horizon 20G 7.2G 12G 39% /opt/vmware/horizon4. Run
'df -h'command to verify the allocated space. - Run the below command on the appliance to identify the disk and associate SCSI ID.
Additional Information
Administrators increase the VIDM root (/) partition because it can become 100% full, this causes the VIDM UI to be inaccessible.
If the root (/) partition has filled to 100%, the UI may still be inaccessible after increasing the disk size.
This is due to the config-state.json being corrupt after the disk reached 100%.
This is due to the config-state.json being corrupt after the disk reached 100%.
Feedback
Yes
No
Powered by
