df -h' command output shows the /opt/vmware/support as 100% usage.vr-appliance[ ~ ]$ df -hFilesystem Size Used Avail Use% Mounted ondevtmpfs 4.0M 0 4.0M 0% /devtmpfs 7.8G 1.0M 7.8G 1% /dev/shmtmpfs 3.2G 1000K 3.2G 1% /runtmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup/dev/sda3 18G 5.0G 12G 30% /tmpfs 7.8G 4.7M 7.8G 1% /tmp/dev/sda2 238M 36M 190M 16% /boot/dev/mapper/support_vg-heapdump 3.9G 96K 3.7G 1% /opt/vmware/heapdump/dev/mapper/support_vg-vrmsdb 9.8G 327M 9.0G 4% /var/lib/vrmsdb/dev/mapper/support_vg-logs 975M 293M 632M 32% /opt/vmware/logs/dev/mapper/support_vg-support 2.0G 1.9G 0 100% /opt/vmware/supporttmpfs 1.6G 0 1.6G 0% /run/user/666vSphere Replication
/opt/vmware/support became full due to the orphaned HMS Support bundle in /opt/vmware/support/hms folder.
Support bundle generated from the CLI will be saved in the /opt/vmware/support/hms folder and will not get cleanup automatically. Support bundle generated from VAMI UI will normally clean-up automatically once the bundle is generated. However, if any issues reported during the support bundle generation can cause the clean-up to be skipped and leaving behind orphaned folders and files in /opt/vmware/support/hms. Manual cleanup is required to free up the space.
Verify the space confirmed by the /opt/vmware/support/hms folder using below command.
du -sh /opt/vmware/support/hms
Note: Take the snapshot of the vSphere Replication before performing the below steps.
rm -rf /opt/vmware/support/hms/HSB*