Symptoms:
'df' command confirms that /dev/mapper/support_vg-vrmsdb is 100% full
Issue appears to have occurred after an in-place upgrade of the vSphere Replication appliance.
Filesystem Size Used Avail Use% Mounted ondevtmpfs 3.9G 0 3.9G 0% /devtmpfs 3.9G 28K 3.9G 1% /dev/shmtmpfs 3.9G 740K 3.9G 1% /runtmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup/dev/sda4 14G 2.7G 11G 21% /tmpfs 3.9G 164K 3.9G 1% /tmp/dev/sda2 238M 25M 201M 11% /boot/dev/mapper/support_vg-logs 975M 377M 548M 41% /opt/vmware/logs/dev/mapper/support_vg-vrmsdb 9.8G 79M 9.2G 1% /var/lib/vrmsdb/dev/mapper/support_vg-support 2.0G 462M 1.4G 26% /opt/vmware/support/dev/mapper/support_vg-heapdump 3.9G 3.7G 0 100% /opt/vmware/heapdumptmpfs 797M 0 797M 0% /run/user/666
heapdump seems to be 100% full
vSphere Live Recovery 9.x
1) Run lsblk command to confirm that the vSphere Replication DB is on the second disk, and on a logical volume:
2) Confirm the LVM physical volume size: pvs
3) Increase the disk on the vSphere Replication VM from 17 GB to, say, 20 GB. (You will not be able to increase if snapshots are present)
4) Resize the physical volume: pvresize /dev/sdb
5) Reboot the vSphere Replication appliance
6) Re-run pvs command, to show added free space: lvdisplay
lvextend -l +100%FREE /dev/support_vg/heapdump
7) Resize the file system:
resize2fs /dev/support_vg/heapdump
8) Confirm available, used and free space by re-running df -h command
9) Reboot the VR appliance and from the VAMI complete "Save and restart service".