How to fix SQLITE_IOERR_WRITE: Disk I/O error during write in SQLite

# Check current permissions
ls -la /path/to/database.db
ls -la /path/to/database/directory/

# Ensure read/write permissions for the owner
chmod 644 /path/to/database.db
chmod 755 /path/to/database/directory/

# If needed, change ownership to the application user
chown appuser:appgroup /path/to/database.db
chown appuser:appgroup /path/to/database/directory/

# Check if filesystem is mounted and writable
df -h /path/to/database/directory/
mount | grep /path/to/mount

# Check filesystem for errors (requires root/admin)
# On Linux ext4 filesystem:
sudo fsck -n /dev/sdX  # Use appropriate device

# Check dmesg for I/O errors
dmesg | grep -i "i/o error"
dmesg | grep -i "disk error"

sudo mount -o remount,rw /path/to/mount

# Check available disk space
df -h /path/to/database/directory/

# Check user disk quotas
quota -v

# Check inode availability (can cause write failures even with free space)
df -i /path/to/database/directory/

// In C/C++ applications
sqlite3_extended_result_codes(db, 1);

int rc = sqlite3_exec(db, sql, NULL, NULL, &err_msg);
if (rc != SQLITE_OK) {
    int extended_code = sqlite3_extended_errcode(db);
    int system_errno = sqlite3_system_errno(db);
    fprintf(stderr, "Extended error: %d, System errno: %d\n",
            extended_code, system_errno);
}

# In Python with sqlite3 module
import sqlite3

conn = sqlite3.connect('database.db')
# Extended error codes are enabled by default in Python
try:
    conn.execute('INSERT INTO table VALUES (?)', (value,))
except sqlite3.OperationalError as e:
    print(f"Error: {e}")
    # Check underlying system error if available

// In Node.js with better-sqlite3
const Database = require('better-sqlite3');
const db = new Database('database.db');

try {
  db.exec('INSERT INTO table VALUES (?)');
} catch (err) {
  console.error('Error code:', err.code);
  console.error('Error message:', err.message);
}

# List all database-related files
ls -la /path/to/database.*

# Common SQLite auxiliary files:
# database.db-journal  (rollback journal)
# database.db-wal      (Write-Ahead Log)
# database.db-shm      (shared memory file)

# Verify directory allows file creation
touch /path/to/database/directory/test-write
rm /path/to/database/directory/test-write

-- Check current journal mode
PRAGMA journal_mode;

-- Try WAL mode (better concurrency)
PRAGMA journal_mode=WAL;

-- Or MEMORY mode (faster but less durable)
PRAGMA journal_mode=MEMORY;

# Check if SELinux is enforcing
getenforce

# Check for SELinux denials
sudo ausearch -m avc -ts recent | grep sqlite

# If needed, adjust SELinux context
chcon -t user_tmp_t /path/to/database.db

# Check AppArmor status
sudo aa-status

# Check for denials in logs
sudo journalctl | grep DENIED | grep sqlite

-- Check database integrity
PRAGMA integrity_check;

-- Check for corruption in freelist
PRAGMA freelist_count;

-- Get quick check (faster but less thorough)
PRAGMA quick_check;

# Dump and restore the database
sqlite3 corrupted.db .dump > backup.sql
sqlite3 new.db < backup.sql

# Verify the new database
sqlite3 new.db "PRAGMA integrity_check;"

import sqlite3

conn = sqlite3.connect('database.db')
cursor = conn.cursor()
cursor.execute('PRAGMA integrity_check')
result = cursor.fetchone()
if result[0] == 'ok':
    print('Database is healthy')
else:
    print(f'Database issues detected: {result}')