WiredTiger: No space left on device MongoDB Origin: Data OSI layer 7 · Application Last updated 5 Nov 2026

MongoDB: WiredTiger error (28) [...] No space left on device / Fatal assertion 28558 ... disk full

MongoDB ran out of disk space on the data volume and stopped or refuses writes.

Exact message you may see WiredTiger error (28) No space left on deviceNo space left on device mongodFatal assertion 28558 disk fullWT_PANIC: WiredTiger library panicOutOfDiskSpace mongod
Explore the map of this error Full error map →
Seen on: MongoDB Linux

Meaning

Free space immediately (old logs, other files), expand the volume, then restart. Drop unused collections/indexes, compact (compact or resync the node), and add monitoring/alerts at 80% disk. Journal and diagnostic.data can be large; rotate logs with logRotate.

Common causes

  • Data volume full
  • Logs/diagnostic data growth
  • Unbounded collections (TTL missing)
  • Oplog or temp files for large sorts
  • Backups stored on the same disk

⚡ Quick fix

  1. Free space: delete old logs/backups, expand disk
  2. Restart mongod after freeing space
  3. Add TTL indexes and retention; monitor disk

Detailed fix by platform

Linux

  1. df -h /var/lib/mongodb && du -sh /var/lib/mongodb/* | sort -h | tail && sudo journalctl -u mongod -n 30

How to diagnose

  1. Disk — Used %?
  2. Largest — What consumes?
  3. Retention — TTL?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

Atlas: bad auth: Authentication failed — MongoServerError: bad auth : Authentication failed. (Atlas user / special characters in password) (MongoDB)Atlas: bad auth: Auth…BSONObj size is invalid / exceeds maximum document size (16MB) — MongoServerError: BSONObj size: 17825792 (0x1100000) is invalid. Size must be between 0 and 16793600(16MB) (MongoDB)BSONObj size is inval…Can't connect from another host (bindIp 127.0.0.1) — MongoDB: connection refused / timed out from a remote host — mongod bindIp defaults to 127.0.0.1 (MongoDB)Can't connect from an…FailedMount — Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition (Kubernetes)FailedMountmongod exited with code 14 (data dir permission / lock) — mongod: Process exited with status 14 — Exception in initAndListen: IllegalOperation: Attempted to create a lock file on a read-only directory (MongoDB)mongod exited with co…mongod killed by OOM killer — MongoDB: Out of memory: Killed process (mongod) — WiredTiger cache + queries exhausted RAM (MongoDB)mongod killed by OOM …MongoDB Atlas: connection timed out — IP not whitelisted — MongoServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted (MongoDB)MongoDB Atlas: connec…Multi-Attach error — Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another (Kubernetes)Multi-Attach errorWiredTige…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.