Problem
When checking the size of a file blob store, users may notice discrepancies among the following size calculations:
• du -sh <file blob store path> → Shows the total disk usage of the blob store directory.
• Total size of the blob store on the UI → Displays the total size of stored blobs, including soft-deleted ones, but excludes temporary files.
• Sum of the sizes of all repositories using the blob store → Relies on metadata stored in the database, excluding soft-deleted components and assets.
These differences occur due to variations in how each method calculates size.
Breakdown of Each Calculation
1. du -sh <file blob store path> : Measures disk usage by including all files within the blob store directory.
2. Blob store size on the UI: Only counts blobs stored in <blob store path>/content, excluding temporary files in <blob store path>/content/tmp
3. Repository size: Uses metadata from the database but does not account for soft-deleted components or assets.
Possible causes
1. du -sh <file blob store path> reports a much larger size than the UI
• This can happen if the <blob store path>/content/tmp directory contains a large number of temporary files.
2. The total size of the blob store on the UI is greater than the sum of all repository sizes
• This usually indicates that many soft-deleted blobs are still on disk but haven’t been hard-deleted.
Solution
To address these discrepancies, follow these steps:
1. Clear temporary files:
Run the Admin - Delete blobstore temporary files task to remove unnecessary temporary blobs.
2. Hard-delete soft-deleted blobs:
Run the Admin - Compact blob store task to permanently remove soft-deleted blobs from the disk.
3. Recalculate blob store size:
Run the Repair - Recalculate blob store storage task and compare the results.
Please raise a support ticket for further assistance if the issue persists after these steps.