SQLite: disk I/O error (SQLITE_IOERR)
SQLite couldn't read or write the database or its journal/WAL files.
disk I/O errorsqlite3.OperationalError: disk I/O error Meaning
Typical on network/cloud-synced folders, full disks, read-only or permission-restricted directories, or when the -wal/-shm files are on a filesystem without proper locking. Move the database to local disk, free space, fix permissions, and never put WAL databases on NFS/SMB/Dropbox.
Common causes
- Database on a network share or synced folder
- Disk full or quota
- Directory not writable (journal can't be created)
- Corrupted/removed -wal/-shm file
- Container volume with wrong permissions
⚡ Quick fix
- Use a local disk path
- Check
df -hand directory permissions - Delete stale -wal/-shm only after a clean close
Detailed fix by platform
Linux
- bash
df -h . ls -l app.db* sqlite3 app.db "PRAGMA integrity_check;"
How to diagnose
- Location — Local disk?
- Free space — Available?
- Directory — Writable?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026