Workaround for Volumes Limited by Cluster Size

In some cases, you may find that a volume onboarded to Lucidity is unable to expand beyond a certain size. This limitation is not due to Lucidity itself, but is inherent to how Windows/NTFS file systems handle cluster sizes.

For example, a volume formatted with an 8 KB cluster size can expand only up to 32 TB — regardless of available capacity or Lucidity scaling policies.

This guide outlines the steps to work around this limitation by creating a new volume with a larger cluster size, migrating data, and re-onboarding.

Recommended Steps Before Onboarding

1. Create a New Volume with the Desired Cluster Size

   • Create a new disk with an appropriate cluster size based on your workload needs and expected future growth. Check the Reference Table below.

2. Migrate Data and Applications

   • Attach the newly created volume to the same instance.

   • Copy all required data from the existing Lucidity-managed disk to the new disk.

   Note

   Ensure no backups are running and applications are not actively using the volume during migration. This minimizes risks of performance degradation or data corruption.

3. Validate Functionality

   • Reconfigure applications and services to point to the new volume.

   • Thoroughly validate that:

     1. All data has been successfully copied.

     2. Applications function correctly with the new volume.

4. Onboard the New Volume to Lucidity

   • Once validated, onboard the new volume into Lucidity.

5. Deboard the Old Volume

   • After successfully onboarding the new volume, deboard the old volume from Lucidity.

Reference Table: Cluster Size vs Max Volume Size