Postgres volume is full, database crashed and cannot recover
k4hr
PROOP

a month ago

Hi. My Railway Postgres volume ran out of disk space and the database can no longer start or recover.

Deployment ID: 7c83d9cb-7f70-4f97-873a-2e88323e9e44

Project: ATELIA

Service: Postgres

Diagnostics says:

- the Postgres volume is full

- filesystem became read-only

- Postgres cannot start or recover while the volume is full

- redeploy also fails for the same reason

Please help to:

1. resize the volume, or

2. assist with recovery / restore from backup if needed

Relevant error:

PANIC: could not fdatasync file ... No space left on device

could not write to file "postmaster.pid": No space left on device

PANIC: could not open file ... pg_control: Read-only file system

Solved

2 Replies

Railway
BOT

a month ago

Your Postgres service is currently in a FAILED state due to the full volume. You can resolve this by opening the volume settings on your Postgres service and clicking "Live Resize" to increase the capacity. Since the volume is at 100%, the system will perform an offline resize with automatic data integrity checks and restart the service, which should allow Postgres to recover. If you have backups configured, you can also restore from a previous backup via the Backups tab on the service.


Status changed to Awaiting User Response Railway 26 days ago


Status changed to Awaiting Railway Response Railway 26 days ago


24 days ago

Hi k4hr,

I just took a look at your PostgreSQL database and I can see it's been deployed successfully since you opened this thread. It looks like it's now in a healthy state and the volume resize + redeploy sorted things out.

I am going to mark this thread as solved, but feel free to respond here again if you need help with anything else.

Thanks!


Status changed to Awaiting User Response Railway 24 days ago


Status changed to Solved mykal 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...