2 months ago
My Postgres instance is stuck in a crash loop. It ran out of disk space during WAL recovery after a large DELETE operation. I upgraded the volume from 0.5GB to 5GB but the filesystem still reports "No space left on device" and Postgres cannot complete startup.
Error in logs: FATAL: could not write to file "pg_wal/xlogtemp.29": No space left on device
The volume resize does not seem to have propagated to the filesystem. I need help getting the filesystem resized so Postgres can complete recovery and start up.
Project: n8n (w/ postgres) Service: Postgres Volume: postgres-volume
- Volume ID:
fd0fafda-6e71-4803-931f-203e97da60f3 - Service: Postgres (ID:
1bcccdbd-e498-48df-9d66-08048fbcbbf7) - Issue: Volume is full with incomplete WAL file. Already upgraded to 5GB but filesystem wasn't expanded. Need filesystem-level resize while volume is offline.
- Project: glorious-dedication
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! The volume resize from 0.5 GB to 5 GB didn't fully apply on our end, which is why Postgres couldn't complete WAL recovery. We've fixed it and redeployed your Postgres service. You should now have ~4.7 GB of available disk space.
We've also shipped a fix to prevent this from happening on future volume resizes.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago