Symptoms:
1. Volume size is expanded according to VEA gui but file system free space has not grown in explorer.
2. Volume size and file system size do not match up closely and differ by a large amount. (>1GB)

Two possible solutions are available:

Solution 1:
If you are logged onto the Microsoft Windows operating system through terminal services, end all the terminal service sessions running on the server and log yourself off as well. Log back to this server. If this did not fix the issue proceed to the next method below.

Solution 2:
Run a following command on affected server:
vxvol [-g] growfs <VolumeName> | DriveLetter |<VmName|DrivePath> [<length>]
If the optional parameter [<length>] is not used, the command would try to grow the
file system size to the full volume size.

eg. vxvol growfs g:
- This will try and expand the filesystem to the maximum size of the volume that it resides in.

The following attributes apply:
-g<DynamicDiskGroupName> - Needed only if you are using the internal volume
name parameter
<VolumeName> - The path name of the volume, such as \Device\HarddiskDmVolumes\DG1\Volume1
> - The drive letter of the volume
- Internal name of the volume; requires the use of the -g option, such as -gDG1 Volume1
- A volume that is mounted on an NTFS folder; it is indicated by a path to that folder
<length> - Size of the volume in MB. If no size is indicated, the volume is grown to the maximum size (not needed in most cases)

Note Any growth is limited to a maximum of 2 TB every time this command is run. The
file system usable space is in general somewhat smaller than the raw volume size,
since the file system itself occupies space. Only use this command when you see a
large difference between the volume size and the file system capacity.