The /vashare disk can grow quickly if Personal Storage is enabled.
To constrain growth, set disk space quotas. See Managing and Restricting Filr-Based Storage
in the Filr 4.3: Administrative UI Reference.
The /vastorage disk will see the most growth because this is where the indexes reside.
SQL disk space growth is confined to the database (/vastorage on the MySQL appliance).
Depending on the current size of /vastorage, you should expand /vastorage to allow for growth as follows:
After synchronizing the first 20 million files, run the following query on the database.
SELECT sum(round(((data_length + index_length) / 1024 / 1024 / 1024), 2)) as "Size in GB" FROM information_schema.TABLES WHERE table_schema = "<database name>"
Based on the results, calculate the disk space required for 100 Million files.
Include anticipated growth that in the total.
Set the DB innodb_buffer_pool_size to 66-75% of the total memory available to the appliance.
This parameter is set on initial configuration with new installs, but if the HyperVisor guest OS's memory increases, this parameter needs to be manually set in the /etc/my.cnf file.
In /etc/my.cnf, the exact setting is
innodb_buffer_pool_size = 2048M
The byte specifier is mandatory.
Setting this to more than the available memory on the system prevents the database from starting.