Issue
The vacuum tool in Metadefender Core fails to free up disk space or does not free up much space after execution. The vacuum_running.log log file contains errors similar to the following:
INFO: vacuuming "scan.scan_result_1" vacuumdb: error: vacuuming of table "scan.scan_result_1" in database "metadefender_core_0nten9" failed: ERROR: could not extend file "base/16384/860193032.13": No space left on device HINT: Check free disk space.
Resolution
The ometascan-db-vacuum tool requires sufficient free disk space to create a backup file during execution. Specifically, it needs at least 1.5 times the size of the largest table in the database.
Steps to Resolve
Check the size of the largest table:
- Follow this docs to generate MD Core support package
- Extract the support package zip file
- Check the file ometascan-xxxx.zip/database/biggest_tables.csv to identify the size of the largest table
Verify available disk space: Ensure that the disk where the Metadefender Core database resides has at least 1.5 times the size of the largest table available as free space.
Increase disk size (if necessary): If insufficient disk space is available, increase the disk size accordingly.
Re-run the vacuum tool: After increasing the disk size, execute the
ometascan-db-vacuumtool again.
If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
