Cloud SQL instance storage full — instance becomes read-only / suspended
The Cloud SQL disk reached its limit, so writes fail and the instance can enter a read-only state.
Cloud SQL storage fullThe instance is read-only because the disk is fullERROR: could not extend file: No space left on device Cloud SQLCloud SQL disk fullCloud SQL instance suspended storage Meaning
Enable automatic storage increase, manually increase the disk (it can't be shrunk), find large tables/binlogs/temp data, and clean up (purge binary logs, drop unused data). PostgreSQL WAL accumulating from a stuck replication slot is a common cause.
Common causes
- Auto storage increase disabled
- Large tables or binary logs/WAL
- Replication slot not consumed (PostgreSQL)
- Temp files from big queries
- Point-in-time recovery logs
⚡ Quick fix
- Increase storage and enable automatic increase
- Drop/archive large data and purge logs
- Drop abandoned replication slots
Detailed fix by platform
Shell
gcloud sql instances patch INSTANCE --storage-size=200GB --storage-auto-increase
How to diagnose
- Disk — 100%?
- Auto increase — Enabled?
- Slot/binlog — Growing?
🔧 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
- 1114 MySQL ERROR 1114 (HY000): The table 'x' is full
- 53100 ERROR: could not extend file "base/…": No space left on device
- AuthenticationFailed Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed)
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. 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