Morpheus shows incorrect capacity after extending GFS2 datastore in HPE VME

[SevanSardarian]

I’m running HPE VME Essentials with a GFS2-based shared datastore. Recently, I extended the underlying storage (LUN / block device) and successfully grew the filesystem on all cluster nodes using the standard Linux/GFS2 procedure.
However, in the Morpheus GUI, the datastore capacity still shows the old size or inconsistent values, even after refreshing the datastore.

[Mansoor1]

Expanding a GFS2 filesystem at the OS level does not automatically update the datastore size shown in VME.
 VME does not dynamically re-detect filesystem growth for existing shared datastores.
This is expected behavior, not a failure of GFS2 or the OS.

This behavior is expected with GFS2-backed shared datastores in HPE Morpheus VM Essentials.As per VM Essentials documentation, GFS2 is a supported shared filesystem datastore type, and datastore capacity is discovered when the datastore is initially added/onboarded into VME.The documentation describes datastore onboarding and availability management, but it does not state that VME dynamically re-detects filesystem size changes after an OS-level grow operation (for example, extending a LUN and running gfs2_grow).In practice, when a GFS2 filesystem is expanded at the Linux level:

• All cluster nodes correctly see the new size
• Existing workloads can consume the additional space

The datastore capacity shown in the VME UI remains at the originally detected sizeA datastore “Refresh” in the UI updates metadata and availability, but does not trigger a re-read of filesystem geometry. Restarting services or waiting for polling intervals does not update the displayed size.The following workarounds are available:

• Remove and re-add the datastore
•  If operationally possible, remove the datastore from VME and re-add it using the same mount point. This causes VME to rediscover the datastore and record the updated capacity. Ensure no active workloads are using the datastore before doing so.
• Continue using the expanded capacity at the OS level
•  The additional space is available to workloads at the filesystem level even though the VME UI continues to display the original size.