Skip to content
Postgres disk-full recovery — inspect safe reclaim without storage expansion
bhagirathibarik0282-sudo
OP

2 hours ago

My Postgres is stuck in disk-full recovery.

Project: courteous-perception

Service ID: 55871ef6-c0ed-48af-8819-8f7a6c6ece0e

Volume: postgres-volume — 5 GB

Usage: 4.9969 GB

Error:

PANIC: could not write to file

"pg_logical/replorigin_checkpoint.tmp":

No space left on device

Please inspect filesystem usage for a recovery option WITHOUT expanding storage.

Identify any safely removable non-database files.

Preserve all database rows and WAL files.

Do not delete, reset, restore or resize without my approval.

Awaiting User Response

3 Replies

Railway
BOT

2 hours ago

Your postgres-volume is at about 4,997 MB of its 5,000 MB, which is also the largest volume size available on the Hobby plan, so Postgres has no room to write and keeps failing on startup.

You can inspect the volume's contents yourself without changing anything using railway volume browse / or railway volume files list / from the CLI, which show what is taking up the space under the data directory (managing volume files). Files such as old server logs in a log directory, if present, are outside the database rows and WAL, while anything under base, global or pg_wal is part of the database itself.

If inspection shows nothing removable, the remaining route is more space: the Pro plan allows self-serve volumes up to 1 TB, and a resize can then be done from the volume's settings (volume size limits).


Status changed to Awaiting User Response Railway • about 2 hours ago


Railway

Your `postgres-volume` is at about 4,997 MB of its 5,000 MB, which is also the largest volume size available on the Hobby plan, so Postgres has no room to write and keeps failing on startup. You can inspect the volume's contents yourself without changing anything using `railway volume browse /` or `railway volume files list /` from the CLI, which show what is taking up the space under the data directory ([managing volume files](https://docs.railway.com/volumes#using-the-volume)). Files such as old server logs in a `log` directory, if present, are outside the database rows and WAL, while anything under `base`, `global` or `pg_wal` is part of the database itself. If inspection shows nothing removable, the remaining route is more space: the Pro plan allows self-serve volumes up to 1 TB, and a resize can then be done from the volume's settings ([volume size limits](https://docs.railway.com/volumes/reference#size-limits)).

bhagirathibarik0282-sudo
OP

2 hours ago

I still need help. This remains unresolved. Please have a Railway support engineer inspect the existing mounted postgres-volume and provide exact paths and sizes of any reclaimable non-database files. My connected tooling cannot execute container shell or volume-file inspection, and I am working from mobile. Please confirm whether server log files or core dumps actually exist on this volume, and whether any filesystem-reserved space is available. Do not assume these are present. I need a recovery option without expanding storage. Preserve all database rows and WAL files. No deletion, reset, restore, filesystem changes, or resize without my explicit approval. Please report inspection findings first.


Status changed to Awaiting Railway Response Railway • about 2 hours ago


Railway
BOT

2 hours ago

The volume details available to us show postgres-volume using about 4,997 MB of its 5,000 MB, but they report total usage only, not individual files, so we can't give you a list of paths and sizes or confirm whether server logs, core dumps, or reserved filesystem space exist on it.

Getting that per-file breakdown means looking at the volume's contents directly, using the CLI commands from our earlier reply (railway volume browse or railway volume files list) from any computer where the Railway CLI is installed. Neither command changes anything on the volume.


Status changed to Awaiting User Response Railway • about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...