Disks larger than 2TB do not increase the /storage/db volume in vROps

Products

• VMware Aria Suite

Issue/Introduction

Note: If this article does not resolve your issue, see Troubleshooting Storage Issues in vRealize Operations (83239).

Symptoms:
When a virtual disk larger than 2TB is added to one or more VMware vRealize Operations nodes:

• After a reboot, the size of the /storage/db partition is not increased by the size of the recently added virtual disk.
• If the pre-configured 250GB virtual disk is increased to a size larger than 2TB prior to the first power-on operation, the /storage/db file system is not created. Under the / directory, /storage/db will be a directory and the / file system may fill quickly.

Environment

VMware vRealize Operations 8.3.x
VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations 8.x
VMware vRealize Operations 8.4.x
VMware vRealize Operations 8.0.x
VMware vRealize Operations 8.2.x
VMware vRealize Operations 8.1.x
VMware vRealize Operations Manager 7.5.x

Cause

This is an expected behavior in VMware vRealize Operations. The underlying Linux operating system does not recognize a virtual disk larger than 2TB.

Resolution

If a virtual disk larger than 2TB is added to VMware vRealize Operations, shut down the node, remove the virtual disk and add multiple smaller virtual disks.

If the pre-configured 250GB virtual disk is increased to a size larger than 2TB prior to the first power-on operation, discard the vRealize Operations installation and initiate a new deployment.