2 months ago
Hi Railway Support Team,
I am writing to report a critical issue regarding my Postgres volume.
I have recently resized my Postgres volume from 500MB to 5GB because of a disk space error. However, even after the resize and multiple restarts, the service continues to crash with the following error: "FATAL: could not write to file 'pg_wal/xlogtemp': No space left on device"
It seems like the underlying file system (ext4) was not properly expanded during the volume resize process. My project is currently halted, and I cannot perform a "Wipe Volume" because I do not have a recent backup of my n8n workflow JSON files.
Could you please manually trigger the filesystem resize (resize2fs) for my Postgres volume or investigate the backend status?
- my ID: jizjwsb@gmail.com
I look forward to your prompt response.
Best regards,
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hi there,
I can see the volume resize from 500MB to 5GB didn't fully apply, which is causing the disk space errors. We can fix this on our end.
However, I noticed your project is currently scheduled for deletion. If you still need this project and want us to proceed with the fix:
- Cancel the project deletion from your dashboard
- Reply here to confirm
Once confirmed, I'll apply the fix and redeploy your Postgres service. You should then see the full 5GB available.
Status changed to Awaiting User Response Railway • about 2 months 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 • about 1 month ago