disk I/O error SQL Origin: Data OSI layer 7 · Application Last updated 18 Nov 2026

SQLite: disk I/O error (SQLITE_IOERR)

SQLite couldn't read or write the database or its journal/WAL files.

Exact message you may see disk I/O errorsqlite3.OperationalError: disk I/O error
Seen on: SQLite Linux

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

  1. Use a local disk path
  2. Check df -h and directory permissions
  3. Delete stale -wal/-shm only after a clean close

Detailed fix by platform

Linux

  1. bash
    df -h .
    ls -l app.db*
    sqlite3 app.db "PRAGMA integrity_check;"

How to diagnose

  1. Location — Local disk?
  2. Free space — Available?
  3. 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:

Where this error sits

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

database or disk is full — SQLite: database or disk is full (SQLITE_FULL) (SQL)database or disk is f…datatype mismatch — SQLite: datatype mismatch (SQLITE_MISMATCH) (SQL)datatype mismatchdisk full — Compute Engine VM disk full: No space left on device — resize the persistent disk and filesystem (Google Cloud / Firebase)disk fullmalformed database — sqlite3.DatabaseError: database disk image is malformed (SQL)malformed databasereadonly database — sqlite3.OperationalError: attempt to write a readonly database (SQL)readonly databaseSQLITE_BUSY — sqlite3.OperationalError: database is locked (SQLITE_BUSY) (SQL)SQLITE_BUSYtable is locked — SQLite: database table is locked (SQLITE_LOCKED) (SQL)table is lockedtransaction — SQLite: cannot start a transaction within a transaction (SQL)transactiondisk I/O …

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.