We're experiencing a critical issue with our PostgreSQL 17.9 deployment on Railway. Despite expanding the volume to 250GB several days ago, SSH access shows the Postgres data directory is reporting only 434MB total space with 424MB used (100% full).

Symptoms:

• Backend login failing: 401 Unauthorized errors
• All write operations fail: FATAL: could not write init file: No space left on device
• psql client cannot connect to the database
• df -h in the container shows /dev/zd10416 at 434M total, 424M used, 0 bytes free

Environment Details:

• PostgreSQL 17.9 on Railway
• Instance had volume expanded to 250GB ~3 days ago
• Data directory: /var/lib/postgresql/data/pgdata
• Disk usage breakdown:
  • base/: 388M (actual data tables)
  • pg_wal/: 33M (write-ahead logs)
  • pg_xact/: 3.5M

Questions:

1. Did the volume expansion to 250GB complete successfully, or is there a separate container storage limit?
2. Why does df -h show only 434M total despite the 250GB allocation?
3. Does the Postgres service need to be manually restarted to recognize the new volume size?

Impact:

Production application is completely offline. Users cannot log in. All database writes are blocked.