a month ago
Hi Railway team,
My persistent volume isn't surviving deploys despite the volume ID staying the same. Need help diagnosing.
Project: zippy-wonder
Service: agentic-task-manager
Volume: agentic-task-manager-volume (ID: vol_ytzmzyyh1ah0qvpq)
Mount path: /data
Size: 5 GB
The problem
After every deploy, the contents under /data come up empty even though the volume ID is unchanged. Specifically:
- /data/output/sent_log.jsonl (my append-only audit log) is gone
- All run-history directories under /data/output// are gone
- A persistence marker file I drop at /data/output/.persistence_marker resets every deploy
- Please check whether the volume is actually being preserved across deploys or whether each deploy is mounting a fresh empty volume.
If there's a config I'm missing on my end, please point me at it. Happy to share my diagnostic endpoint output if useful.
Thanks.
1 Replies
a month ago
Your volume is attached and in READY state, but the mount path stored in our system is /data (with a trailing space) rather than /data. This means the volume is mounted at a slightly different path than where your application writes, so your app's writes to /data/output/ go to the container's ephemeral filesystem instead of the volume. The ~150 MB currently on the volume is just filesystem metadata overhead, confirming nothing substantial is being written to it. You can fix this by updating the mount path in your service's volume settings to remove the trailing space, then redeploying.
Status changed to Awaiting User Response Railway • about 1 month ago
24 days 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 • 24 days ago