1675
MariaDBERRORCommonStorage EngineHIGH confidence
I/O write error occurred
Production Risk
Critical — write errors halt transactions and may corrupt data.
What this means
MySQL encountered an I/O write error while attempting to write data to a tablespace file, typically indicating disk full, permissions, or hardware failure.
Why it happens
- 1Disk is full or the filesystem quota is exceeded.
- 2The .ibd file or directory has incorrect permissions.
- 3Hardware failure or storage controller errors.
How to reproduce
trigger — this will error
trigger — this will error
INSERT INTO large_table SELECT * FROM source; -- disk fills up
expected output
ERROR 1675 (HY000): Got error 28 when writing file './mydb/t.ibd' (OS errno 28 - No space left on device)
Fix 1
Free disk space
Free disk space
-- Remove old binary logs: PURGE BINARY LOGS BEFORE NOW() - INTERVAL 7 DAY; -- Or delete old backups/temp files
Why this works
Freeing disk space allows MySQL to resume writes.
Fix 2
Check and fix file permissions
Check and fix file permissions
-- chown -R mysql:mysql /var/lib/mysql
Why this works
Correct ownership allows the MySQL process to write to tablespace files.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 1675 ER_IO_WRITE_ERROR
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev