4 days ago
Hi, two of my persistent volumes are showing much higher "used" space in the dashboard than what's actually on disk, which looks like unreclaimed storage after file deletions:
mayor-whatsapp-poster-volume (id bb8ef4e3-9a5d-4afc-9871-ea7b6cd059d7, service mayor-whatsapp-poster): reports 3.9GB/5GB used, but actual files total ~20MB (verified via df -h and file listing in the console).
whatsapp-bridge-volume (id be3efbe0-8445-43a7-957b-1b32f2000ebd, service Whatsapp Bridge): reports 2.8GB/5GB used, but actual files total ~230MB (mostly whatsmeow_auth.db).
Could you reclaim/trim these volumes on your end? fstrim from inside the container fails with "Operation not permitted" since I don't have raw block-device access.
1 Replies
4 days ago
The dashboard usage metric reflects ZFS-level allocated blocks, not the logical size of live files, so a gap after large deletes is expected. Volumes are mounted with continuous discard, which reclaims some space over time, but the storage layer allocates in 16 KB blocks while ext4 frees in 4 KB blocks, so partially-freed blocks can never be returned and the metric settles permanently above what df/du report. The fstrim failure is also expected since containers lack the required capability. We don't perform manual host-side reclamation, as any reclaim would stop at that same block-size floor. The only way to fully reset a volume's footprint is to migrate the data into a fresh volume and delete the old one. In dollar terms the excess is roughly 6 GB at $0.15/GB-month, so about $0.90/month across both volumes.
Status changed to Awaiting User Response Railway • 4 days ago