Hi Railway Support,

I am experiencing a critical issue with my Postgres service.
The database crashed due to a full disk. I have resized the volume attached to the service from 500MB to 1GB, and finally to 5GB. The Railway UI confirms the volume is resized to 5GB.

However, the service is stuck in a crash loop. Every time it restarts, the logs show the following error during the WAL redo process:
FATAL: could not write to file "pg_wal/xlogtemp.26": No space left on device

It seems the container is not recognizing the expanded file system size, or the volume resize hasn't propagated to the file system level inside the container, preventing the database from completing its recovery sequence.

Service Details:

• Environment: Production

• Service: Postgres

• Current Volume Size: 5 GB (as per Settings)

• Error: No space left on device during startup.

Please help me verify if the volume resize was successful on the file system or if there is a stuck claim on the volume. I need to recover the data urgently.

Thank you.