12 days ago
Hi,
My Postgres service is offline and the volume resize is stuck.
Project ID: 19e60f65-dd9d-4114-b663-a2b0cbaad90f
Service ID (Postgres): 96ae1759-8289-4f1b-b725-d52494ccd343
Volume: postgres-volume
What happened:
-
The volume (500 MB) reached 100% capacity while running n8n
-
Postgres started crash-looping with:
PANIC: could not write to file "pg_wal/xlogtemp.XXXXX": No space left on device
-
I triggered a Live Resize from 500 MB to 5000 MB (Hobby plan)
-
The resize has been stuck on "Resizing volume..." for over 1 hour with no progress
-
Postgres shows "Service is offline", and my Worker service has been crashed for 1 hour
A backup was automatically created before the resize (485 MB, listed under Backups).
Could you please trigger the filesystem resize (resize2fs) on this volume?
The block storage appears to have been allocated but the filesystem operation is stuck.
Thanks a lot for your help.
1 Replies
12 days ago
The volume resize has already completed successfully, with postgres-volume now at 5000 MB (READY state, ~486 MB used). The Postgres service's latest deployment was torn down during the process and did not restart automatically, which is why it shows as offline. Triggering a new deployment from the service's settings (or clicking "Deploy" on the service page) should bring Postgres back up with the full 5 GB available, and the Worker service should recover once Postgres is reachable again.
Status changed to Awaiting User Response Railway • 12 days ago
5 days 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 • 5 days ago