21 hours ago
Hello! I’m running a small Python Discord bot with SQLite on Railway. Its persistent Volume is mounted at /data.
The Volume Usage graph increased from 32.49 MB to 43.26 MB between 04:30 and 09:46 GMT+3 on October 5, 2026. However, repeated console measurements remained unchanged:
du -ah /data
16K /data/lost+found
48K /data/aktarim-oncesi-e3a47146.sqlite3
48K /data/benoh.sqlite3
116K /data
df -h /data
Filesystem Size Used Avail Use% Mounted on
/dev/zd10512 434M 248K 424M 1% /data
I also compared two consistent SQLite backups taken several hours apart. Both were 49,152 bytes and passed integrity checks. One player record and its identity record were added, but existing records remained unchanged and the database file size did not grow.
What does the Volume Usage graph include beyond the usage reported by du and df? Is this discrepancy expected, and does the growing graph value affect billed storage?
I’d appreciate suggestions for investigating this without deleting or recreating the Volume, since it contains persistent game data.
1 Replies
21 hours ago
This is expected and your data is fine. The Volume Usage graph doesn't show the size of your files. It shows how many blocks the underlying storage has allocated for the volume. The filesystem inside your container frees space in 4 KB blocks, but the volume allocates storage in 16 KB blocks. A 16 KB block that is only partly freed can't be given back, so a workload that keeps rewriting small files, which is what SQLite does with every write, sits above what du and df report. Snapshots and backups are not part of this figure.
The figure won't come down to match df. It levels off somewhere above it. That's normal accounting, not something wrong in your container, so you don't need to investigate further or touch the volume.
Billing does use this graph's value. Volume storage is billed on measured usage at $0.15 per GB-month, averaged over the billing period, so around 43 MB comes to well under one cent per month. Provisioned size isn't billed, only usage.
Status changed to Awaiting User Response Railway • about 21 hours ago
Status changed to Solved medenzero • about 20 hours ago