a month ago
Project: intelligent-enchantment Postgres crash-looping with: FATAL: could not write to file "pg_wal/xlogtemp.33": No space left on device Volume was at 500MB/97% full. Resized to 5GB via Live Resize but filesystem didn't expand - container still sees no space. Database completely down. Already submitted support ticket. Need Railway team to manually expand the filesystem.  Status: Your database is currently running (latest deployment is SUCCESS), but you have index corruption from the disk-full event. The error index "bt_result_rows_ticker" contains unexpected zero page at block 175 indicates Postgres couldn't write properly when the disk filled up.
What you need to do:
- Wait for Railway support to expand the filesystem. They'll need to:
- Stop the container
- Expand the ext4 filesystem on the 5GB volume
- Restart Postgres
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey, thanks for the heads up. You were right that the resize didn't fully apply: the underlying disk was expanded, but the layer that Postgres sees was still capped at 500 MB.
I've fixed that and redeployed your Postgres service. You should now see the full 5 GB available.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 27 days ago