Resizing vRA/vRO logs disk (/dev/sdc) is not reflected in the OS
search cancel

Resizing vRA/vRO logs disk (/dev/sdc) is not reflected in the OS


Article ID: 345269


Updated On:


VMware Aria Suite


  • After increasing the size of the logs disk (/dev/sdc) of a vRealize Automation (vRA) or vRealize Orchestrator Appliance (vRO) appliance, and running "vracli disk-mgr resize", the new space is not reflected by OS.
  • Running "vracli disk-mgr" or "df" commands still displays the old overall size.
  • In the "/var/log/disk_resize.log" file, you see entries similar to:
    • "ERROR: Error resizing file system"
    • "Extending logical volume services-logs... New size (5119 extents) matches existing size (5119 extents)"
"ERROR: Error resizing logical volume."


VMware vRealize Automation 8.1.x
VMware vRealize Orchestrator 8.x
VMware vRealize Automation 8.x


This is caused by an invalid logical volume name used while resizing the file system.


This  is resolved in VMware vRealize Automation versions 8.2.

To work around this issue in version 8.1 and earlier:
  1. SSH to the appliance.
  2. Run the command: "vracli disk-mgr resize". The resize procedure will start in up to a minute. Progress could be monitored in the /var/log/disk_resize.log. It is expected to fail while resizing file system for logs disk.
  3. Run the command: "/usr/sbin/resize2fs /dev/mapper/logs_vg-services--logs"
  4. Run the command:
  • For vRA/vRO 8.0: "rm /var/run/disk_stats"
  • For vRA/vRO 8.0.1 and 8.1: "rm /var/vmware/prelude/disk-management/disk_stats"
  1.  Run the command  "vracli disk-mgr" to verify if new disk space is visible.