4 months ago
Volumes like postgres-volume-jpDJ, postgres-2-volume, etcd-1-volume, etcd-2-volume, etcd-3-volume show mountedOn: null in the UI
However, they are actually mounted to their respective services (Postgres, Postgres-2, etcd-1, etcd-2, etcd-3)
This is confusing and could lead users to accidentally delete critical volumes thinking they're unused
1 Replies
4 months ago
Those volumes are genuinely unattached. Your services are currently using different, newer volumes: Postgres and Postgres-2 are mounted to volumes created on 2026-06-08, and etcd-1/2/3 are each mounted to "etcd-wipe-..." volumes. The original volumes you mentioned (postgres-volume-jpDJ, postgres-2-volume, etcd-1-volume, etcd-2-volume, etcd-3-volume) are leftover from before and are not mounted to any service, though they still hold data and incur storage charges. If you no longer need the data in those old volumes, you can safely delete them to stop the storage billing.
Status changed to Awaiting User Response Railway • 4 months ago
Status changed to Solved ninomandelab • 4 months ago