Same ZFS/ext4 filesystem mismatch as thread below— volume shows 5 GB, ext4 still capped
nahmatt
HOBBYOP

a month ago

Description: Project: focused-radiance

Service: Postgres

Workspace: Hobby

I'm hitting the exact same issue sam-a resolved for xxgatsu2 a month ago

(thread: https://station.railway.com/questions/postgres-volume-resized-to-5-gb-but-reco-e183c31c).

Symptoms match precisely:

- Volume shows 5 GB cap in UI

- pg_database_size = 355 MB

- pg_ls_waldir total = 16 MB

- Writes fail with: could not extend file "...": No space left on device

(mdzeroextend / mdextend, errcode 53100)

Please can you run the same fix — expand the ext4 filesystem inside the

volume to match the 5 GB ZFS size?

Happy to provide volume ID once I have access to it.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


a month ago

The 5 GB resize didn't fully apply to the Postgres volume, so writes were still hitting the old limit.

I've applied the fix and redeployed the service. Postgres should now see close to the full 5 GB of available disk space.


Status changed to Awaiting User Response Railway about 1 month ago


Status changed to Solved nahmatt about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...