a month ago
Project ID: e2befdcb-1c27-40dd-8c73-4682109784b5
Environment ID: e5b86456-31db-4d0c-baa6-344eafdc94a5
Postgres Service ID: ad38e292-e56b-4e3e-975c-b77d64cdcff4
Volume ID: dfda2d10-9423-4b5f-b0f2-99b98031c901
Mount path: /var/lib/postgresql/data
Latest Deployment ID: 9f80112a-7815-4b42-95d3-93ee4ff5a8f6
Plan: Hobby
The PostgreSQL volume was resized from 500 MB to 5120 MB. Railway’s control plane reports the new size and no pending changes.
After a full service redeployment, the container still behaves as if the filesystem is limited to 500 MB. PostgreSQL remains in a crash-recovery loop with:
PANIC: could not write to file "pg_logical/replorigin_checkpoint.tmp": No space left on device
Please safely grow/remount the filesystem or perform an offline volume resize. Data preservation is required. Please do not delete or recreate the database or volume.
No destructive operations have been performed. Database integrity will be verified after recovery.
1 Replies
a month ago
The volume resize to 5120 MB was refused because it exceeds the Hobby plan's 5000 MB cap (the error on the pending change reads "Max size of 5000 MB on current plan"). The volume is still at 500 MB with ~496 MB used, which is why PostgreSQL is crash-looping. Railway sizes are SI (5 GB = 5000 MB, not 5120 MB), so updating the staged change to 5000 MB and applying it from the environment's deploy bar will grow the volume and let Postgres complete recovery.
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 • 29 days ago