2 months ago
URGENT: PostgreSQL crash loop - disk full, can't start
Error: "could not create file: No space left on device"
WAL redo failing at startup
Need emergency disk expansion
Pinned Solution
2 months ago
Click on the volume mounted to your postgres instance and increase the max volume, then see if redeploying fixes this.
6 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 PostgreSQL stuck in crash-recovery loop - disk full, cannot complete recovery
🧵 Postgres database crashing due to disk space - Need volume increase immediately
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
Click on the volume mounted to your postgres instance and increase the max volume, then see if redeploying fixes this.
2 months ago
Open Railway Dashboard > Project > PostgreSQL service > Click Volumes > Size (Click Grow button) > Save / Redeploy
2 months ago
It’s already at the max 32GB
bigdaddyaman
Open Railway Dashboard > Project > PostgreSQL service > Click Volumes > Size (Click Grow button) > Save / Redeploy
2 months ago
It’s already at the max 32GB
haydenglassman-git
It’s already at the max 32GB
2 months ago
Just to clarify. When you say “32 GB”, do you mean RAM or PostgreSQL disk volume size? the error "No space left on device" during WAL redo indicates the disk/volume is full, not memory. PostgreSQL won’t start without free disk space.
From Railway volumes docs (https://docs.railway.com/reference/volumes), storage volumes on Pro plans can be grown up to 250 GB so it be good to confirm whether this is actually a Postgres disk volume limit or just a memory limit being referenced.
Status changed to Solved brody • 2 months ago