Postgres crash loop - volume resize not applied
umutimamoglu
PROOP

a month ago

My PostgreSQL service is stuck in a crash-recovery loop after running out of disk space. I resized the volume from 500MB to 1GB via the Railway dashboard, but the resize has not taken effect on the actual filesystem. PostgreSQL fails on every startup with:

FATAL: could not write to file "pg_wal/xlogtemp.33": No space left on device

Volume ID: vol_oe4k3m2ojzyqpysx

Service: Postgres

Project: sweet-stillness

Solved

10 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


gattmanj
PRO

a month ago

I have the exact same issue. I reported 2 days ago and yet to receive a response unfortunately


umutimamoglu
PROOP

a month ago

Did you receive any response?


umutimamoglu

Did you receive any response?

gattmanj
PRO

a month ago

Unfortunately not. What i decided to do was create a new project exactly the same as the last one but with a bigger capacity, then once confirmed working as I want it, I'll delete the old project. Their support is closed on weekends I believe, so Monday/Tuesday for a response to original ticket. Hope this helps mate


gattmanj

Unfortunately not. What i decided to do was create a new project exactly the same as the last one but with a bigger capacity, then once confirmed working as I want it, I'll delete the old project. Their support is closed on weekends I believe, so Monday/Tuesday for a response to original ticket. Hope this helps mate

umutimamoglu
PROOP

a month ago

So, would it be logical to take the last backup, move it to another partition, and then transfer the project there? I'm not a pro at the moment, so I don't know.


gattmanj
PRO

a month ago

Honestly, I'm no problem either. I used claude code within my project folder to rebuild in a new project. Someone more expert might be better to help you if they see this thread


chandrika
EMPLOYEE

a month ago

Hi both, apologies for the slow response here, and thanks for your patience.

@umutimamoglu your Postgres service is currently showing as online in our system, so it looks like you were able to work around this. If you'd still like us to expand any of your volumes to the size you originally requested, let us know which one and we'll take care of it.

@gattmanj glad rebuilding in a new project got you moving. If you'd like us to expand the volume on the original project so it's usable again, let us know.


Status changed to Awaiting User Response Railway about 1 month ago


chandrika

Hi both, apologies for the slow response here, and thanks for your patience. @umutimamoglu your Postgres service is currently showing as online in our system, so it looks like you were able to work around this. If you'd still like us to expand any of your volumes to the size you originally requested, let us know which one and we'll take care of it. @gattmanj glad rebuilding in a new project got you moving. If you'd like us to expand the volume on the original project so it's usable again, let us know.

umutimamoglu
PROOP

a month ago

The reason it appears to be working is because I ran a new volume with a very old backup I had. The problem is with the volume named "postgres-volume-needSupport". Now I've run the original again and it's crashed.

Status changed to Awaiting Railway Response Railway about 1 month ago


umutimamoglu

``` ``` ``` The reason it appears to be working is because I ran a new volume with a very old backup I had. The problem is with the volume named "postgres-volume-needSupport". Now I've run the original again and it's crashed. ``` ``` ```

umutimamoglu
PROOP

a month ago

2a32eab6-e433-4d51-9baa-8f4032cdb9ac (postgres-volume - 5GB)


sam-a
EMPLOYEE

a month ago

The volume resize to 5 GB didn't fully apply to your database's storage. We've corrected this and redeployed your Postgres service. Your data is intact and you should now have approximately 5 GB of available disk space.


Status changed to Awaiting User Response Railway about 1 month ago


sam-a

The volume resize to 5 GB didn't fully apply to your database's storage. We've corrected this and redeployed your Postgres service. Your data is intact and you should now have approximately 5 GB of available disk space.

umutimamoglu
PROOP

a month ago

Thank you very much


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved umutimamoglu about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...