6 hours ago
Volume vixynaserver-volume shows ~75% / ~370 MB usage in Railway Volume Metrics, but inside the mounted volume /app/data, df -h reports only 936 KB used and du shows ~812 KB of actual files. The filesystem is ext4 mounted with discard. Attempting fstrim -v /app/data returns FITRIM ioctl failed: Operation not permitted. Can you verify whether the volume backend has unreclaimed allocated blocks or whether the Volume Metrics data is inaccurate?
1 Replies
6 hours ago
The volume metrics report ZFS-level allocated blocks, not the logical size of live files. When files are deleted or rewritten, freed blocks are only returned to the storage layer via TRIM/discard. Volumes are mounted with continuous discard, so reclamation happens over time, but it will never fully converge to your df/du figure because volumes use 16 KB blocks while ext4 frees space in 4 KB blocks - partially freed 16 KB blocks cannot be returned, so scattered small-file workloads can pin allocation well above guest-visible usage permanently. The fstrim failure is expected since containers lack the required capability. Billing is based on this same metric (GB-minutes at $0.15/GB-month), though the dollar impact of the gap is small. The only way to fully reset the allocation footprint is to migrate your data to a fresh volume and delete the old one.
Status changed to Awaiting User Response Railway • about 6 hours ago