service crashed
cowhub2
HOBBYOP

11 days ago

My PostgreSQL service ran out of disk space and I've upgraded the volume to 5GB, but the database still fails to start with "No space left on device" when writing to pg_wal. The filesystem inside the container has not been resized to match the new volume size.

26-02-25 14:35:14.106 UTC [24] LOG: database system was not properly shut down; automatic recovery in progress

2026-02-25 14:35:14.114 UTC [24] LOG: redo starts at 0/3F9DD320

2026-02-25 14:35:19.935 UTC [24] FATAL: could not write to file "pg_wal/xlogtemp.24": No space left on device

2026-02-25 14:35:19.943 UTC [1] LOG: startup process (PID 24) exited with exit code 1

2026-02-25 14:35:19.943 UTC [1] LOG: terminating any other active server processes

2026-02-25 14:35:19.944 UTC [1] LOG: shutting down due to startup process failure

2026-02-25 14:35:19.959 UTC [1] LOG: database system is shut down

2026-02-25 14:35:19.933 UTC [24] LOG: invalid record length at 0/49C39CD0: expected at least 24, got 0

2026-02-25 14:35:19.933 UTC [24] LOG: redo done at 0/49C39CA8 system usage: CPU: user: 0.60 s, system: 0.23 s, elapsed: 5.81 s

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 11 days ago


sam-a
EMPLOYEE

11 days ago

Volume live resizing, which automatically extends the filesystem to match the new volume size, is only available on the Pro plan and above per our volumes documentation. That said, it appears your volume has already been successfully resized to 5GB. Let us know if you're still experiencing issues.


Status changed to Awaiting User Response Railway 11 days ago


Status changed to Solved sam-a 11 days ago


Loading...