Meilisearch Disk Usage Keeps Growing / No Space Left on Device
Quick answer
Meilisearch's LMDB storage reuses freed space internally but does not return it to the OS, and it doesn't compact by design. Disk can only be reclaimed by a dump and reimport, or by freeing tasks and temp space.
Most likely fix: Free what you can
How to fix it
Try these in order — the most common fix is first.
1. Free what you can
- Delete finished tasks with DELETE /tasks
- Free space on the partition and on /tmp, then resend failed tasks
Did this fix it?2. Shrink the database
- Create a dump with POST /dumps
- Start a fresh instance and import the dump, which rebuilds a compact database
Did this fix it?3. Reduce index size
- Remove fields that are not searchable, filterable, sortable or displayed
- Restrict searchable and filterable attributes
Did this fix it?
Symptoms
data.ms keeps growing after deleting documents; writes fail with no_space_left_on_device.
Why it happens
- LMDB marks deleted space as reusable but doesn't release it to the OS
- Settings, facets and languages inflate index size
- Task queue reached about 10 GiB
- Temporary storage (/tmp) full during indexing
This guide also covers
- meilisearch no space left on device
- meilisearch disk usage high
- meilisearch data.ms size
Still not working?
If Meilisearch keeps failing, you're not alone. See every Meilisearch problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Meilisearch errors
- Meilisearch Tasks Stuck on Enqueued
- Meilisearch Indexing Slow
- Meilisearch Documents Not Showing Up
- Meilisearch Primary Key Error
- Meilisearch Filter Not Working (Attribute Not Filterable)
- Meilisearch Invalid API Key / Missing Authorization Header
- Meilisearch Database Version Incompatible After Upgrade
- Meilisearch High Memory Usage