2 months ago
My Postgres volume filesystem isn't expanding after resize.
Volume ID: d5cf330d-4b26-4286-8f6d-14ed2ba6d79f,
project: ed15d1dc-141b-4132-9c70-15c6cf8b0955.
Volume shows 5GB allocated but only ~1GB used. Postgres crashes on every startup with FATAL: could not write to file "pg_wal/xlogtemp.24": No space left on device.
The underlying filesystem needs a resize2fs.
Data is intact — WAL recovery completes successfully but fails when writing the final recovery file.
4 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
▎ Project: ed15d1dc-141b-4132-9c70-15c6cf8b0955
▎ Volume: d5cf330d-4b26-4286-8f6d-14ed2ba6d79f
▎ Service: Postgres
2 months ago
Could you please help me increase the file system size?I dont see any way for me to do it myself!
2 months ago
Hello! is there a self serve way to do this? We have major dependencies because of this. If I can get a backup of my data I can also migrate to a different service. I'm stuck here! Kindly help
2 months ago
Hey! I took a look at your Postgres volume and confirmed the issue — your recent volume resize didn't fully apply to the disk, which left your database with less space than expected and caused the crash loop.
I've applied the fix on our end and redeployed your Postgres service. You should now have the full ~5 GB of disk space available. Your data is intact.
You'll also need to redeploy your Primary and Worker services from the dashboard, since they crashed while Postgres was down. They should come back up fine now that the database is healthy again.
We've shipped a fix to prevent this from happening on future volume resizes.
Status changed to Awaiting User Response Railway • 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 • 2 months ago