Ravinou
Repository size doesn't match what borg reports
BorgWarehouse version : v3.1.1 Installation type :
- [ ] Docker
- [X] Baremetal (Debian/Ubuntu)
- [ ] Other environment :
Describe the bug
The sizes reported by borg and BorgWarehouse differentiate quite substantially.
For example borg reports a deduplicated size of 521.50 GB, while BorgWarehouse reports 492.3 GB for the same repository.
This is particularily troublesome because the quota is enforced by borg, so on the dashboard everything will look fine, but borg will fail due to the size difference.
My guess would be that borg uses sizes base 10 and BorgWarehouse uses base 2. See this conversion for example: https://www.wolframalpha.com/input/?i=492.3+GiB+in+GB
To Reproduce Steps to reproduce the behavior:
- Create a backup with the
--statsflag - Compare the final deduplicated value with the repository size on the dashboard
Expected behavior These values should be identical for various (and quite frankly obvious) reasons.
Additional context
The client creating the backup is using borg 1.1.16 the host running BorgWarehouse borg 1.2.4.
I updated my borg instances since this issue report to borg 1.4.1 and the issue is still present.
Just today started using BorgWarehouse and created a couple of backups. In borg client it shows All archives Deduplicated size: 7.89 GB; real disk usage Is 7.4GiB (7.9GB). In BorgWarehouse Web UI it shows "0.0% (0.0 GB / 500 GB)". Docker, v3.1.1, borg client 1.4.1
UPD: while reading other issues, found that i'm not running cron jobs that I'm supposed to. After running them, storage usage updated to "1.5% (7.4 GB / 500 GB)"
About original issue: I see this as mismatch of gigabytes and gibibytes. In BorgWarehouse it's wrongly shows gibibytes as "GB" instead of "GiB".
492.310241024*1024 528603099955.2 _/1000/1000/1000 528.6030999552
Yes. The GB vs GiB is the issue I pointed out in my original post.
And in any case I'm glad you figured out the cronjob issue. That's certainly a gotcha.