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.

Exact message you may see 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
Seen on: Google Cloud PostgreSQL MySQL

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

  1. Increase storage and enable automatic increase
  2. Drop/archive large data and purge logs
  3. Drop abandoned replication slots

Detailed fix by platform

Shell

  1. gcloud sql instances patch INSTANCE --storage-size=200GB --storage-auto-increase

How to diagnose

  1. Disk — 100%?
  2. Auto increase — Enabled?
  3. 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:

Where this error sits

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

1114 — MySQL ERROR 1114 (HY000): The table 'x' is full (MySQL)111453100 — ERROR: could not extend file "base/…": No space left on device (PostgreSQL)53100AuthenticationFailed — Azure Storage: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature (AuthenticationFailed) (Azure)AuthenticationFailedAuthorizationPermissionMismatch — Azure Storage: AuthorizationPermissionMismatch (403) — This request is not authorized to perform this operation using this permission (Azure)AuthorizationPermissi…Cloud SQL: failed to connect to instance — Cloud SQL: failed to connect to `host=PROJECT:REGION:INSTANCE user=app database=db`: dial error (timeout) / Cloud SQL Auth Proxy: failed to connect to instance (Google Cloud / Firebase)Cloud SQL: failed to …Cloud SQL: too many connections — Cloud SQL: FATAL: remaining connection slots are reserved / MySQL: ERROR 1040 (08004): Too many connections (Google Cloud / Firebase)Cloud SQL: too many c…ContainerNotFound — Azure Storage: ContainerNotFound / BlobNotFound — The specified container (or blob) does not exist (Azure)ContainerNotFoundCORS: No Access-Control-Allow-Origin (Cloud Storage) — Browser: Access to fetch at 'https://storage.googleapis.com/bucket/file' from origin 'https://app.example.com' has been blocked by CORS policy (Google Cloud / Firebase)CORS: No Access-Contr…storage f…

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.