with -h you would get a binary measure units, so 1.1T is 1.1TiB and this is 1.21TB in SI, used on the dashboard, 148G is 148GiB and this is 158.91GB in SI. Next time I would suggest to use --si instead of -h.
However, if you running 1.109, it again has issues with updating databases on delete.
In short - you need to enable the scan on startup if you disabled it (it’s enabled by default) and restart the node to correct the usage in the databases.
Right now to reduce a time for the filewalkers you may enable a badger experimental feature: