Error Message

Error messages are not always seen, but the following may be logged in the Windows Event Viewer:

ID: V-76-58659-1227
Source:   localhost
Classification: vdsprov class
Brief Description: The VDS file system shrink operation failed. This could be caused by the specified shrink size being greater than the maximum reclaimable free space from the current volume.
Details: The VDS file system shrink operation failed. This could be caused by the specified shrink size being greater than the maximum reclaimable free space from the current volume.
Recommended Action: Decrease shrink size and retry.
 

When this issue occurs, InfoScale is able to increase the volume container size. However, after the container was expanded, the expansion of the File System did not successfully process. The file system expansion is handled by the Windows Operating system via a call to Virtual Disk Service (VDS) from Veritas InfoScale.

In some cases, the expansion fails because the File System is attempting to grow past the maximum volume size based off of the cluster size used for the volume when it was initially created. 
 

Cluster Size	NTFS Max Size
512 bytes	2,199,023,255,040 (2TB)
1024 bytes	4,398,046,510,080 (4TB)
2048 bytes	8,796,093,020,160 (8TB)
4096 bytes	17,592,186,040,320 (16TB) *
8192 bytes	35,184,372,080,640 (32TB)
16384 bytes	70,368,744,161,280 (64TB)
32768 bytes	140,737,488,322,560 (128TB)
65536 bytes	281,474,976,654,120 (256TB)

* 4096 bytes is the default value for volume creation when a volume < 16TB is first created

To ensure the file system expansion did not fail due to an attempt to go over the maximum size, the following steps can be used to determine the cluster size of the volume.

1) Open a command prompt

2) Run command: fsutil fsinfo ntfsinfo <drive_letter>

3) This will provide the Bytes Per Cluster value for the volume.

In this example, 4096 was the cluster size used when the volume was first created, so the maximum size the file system can be is 16TB. 

Once the cluster size is known for the problem volume, use the chart provided above to confirm the expansion will not go past the NTFS limit.

If the expansion exceeds the limit, the only solution is to backup the data, format the volume with a larger cluster size, and restore the data. There is no way to change the cluster unit size without formatting the volume. If the file system expansion did not fail due to cluster unit size, proceed with the steps below.

Veritas InfoScale has a command line option to expand the file system that can be used.

Please follow the steps below.

1) Open an elevated command prompt 

2) Run command: vxvol growfs <drive_letter|DrivePath>

Example:

NOTE: By not specifying a length in the command, it will expand the file system to match the volume container size, which is the expected result, as it will ensure all sectors are used.

3) Once complete, confirm that the volume size in VEA and Windows Explorer is a match.

For Veritas Infoscale on Windows platform, after expanding a volume in the Veritas Enterprise Administrator (VEA), the volume container in VEA shows the updated size, but when viewing the File System size (i.e. via Windows Explorer), it still shows the original size.