pruning output folder size is different from actual folder size

[alfredonodo]

Hi,
I have a problem/question with borg 1.1.5 on ubuntu server 18.04. I already checked the documentation without finding a similar issue. Moreover, I have other machines where borg works without any issue with the same commands.
In few words, borg output after daily pruning is different than actual folder size.
I'm using the following command:

borg init --encryption=repokey-blake2 repository_path
borg create -v --list --filter=AME --progress --stats --exclude-caches --compression lzma,9 destination_folder source_folder
borg prune -v --list --save-space --stats --force --keep-daily=3 --prefix='{hostname}-' repository_path

There are not any error, borg does not delete the old files even if the output show it.

[ThomasWaldmann]

Please reproduce with a current borg version, like 1.1.13.

Also, please be more precise, you did not show the actual "difference".

[pachainti]

Hi,
I'm interested at this too.

[alfredonodo]

Hi,
the latest version on ubuntu 18.04 is 1.1.5 while the latest version available by adding this PPA is 1.1.11. So I installed it, but the result is the same.

---

Archive name: server-root-2020-10-05-14:29:01
Number of files: 37365
Utilization of max. archive size: 0%
------------------------------------------------------------------------------
                       Original size      Compressed size    Deduplicated size
This archive:               12.61 GB             10.37 GB              6.41 MB
All archives:               60.04 GB             49.25 GB             18.06 GB

                       Unique chunks         Total chunks
Chunk index:                   42061               157101
------------------------------------------------------------------------------

Borg pruning old backup

------------------------------------------------------------------------------
                       Original size      Compressed size    Deduplicated size
Deleted data:              -15.03 GB            -12.75 GB            -53.40 MB
All archives:               45.02 GB             36.50 GB             18.00 GB

                       Unique chunks         Total chunks
Chunk index:                   41925               119055
------------------------------------------------------------------------------

The actual size should be 36.5 GB not 45.02 GB.

[ThomasWaldmann]

I still don't get what you mean / what the issue is. Looks pretty consistent to me.

[ThomasWaldmann]

You talk about "folders" - do you mean "archives"?

[alfredonodo]

My question is: why is the archive/folder size displayed by borg different from the archive/folder size displayed by the operating system?

[ThomasWaldmann]

The repository/data/ directory size should be approximately what you see for "all archives" under "deduplicated size" (plus filesystem overhead).

The repository/ directory size is a bit bigger, because there is the repo index and some other files in there also.

[alfredonodo]

As you can see this is almost 3 times the deduplicated size.

du -sh borg_folder
52G	borg_folder

I have other machines where the size of the borg_folder is more or less the same of that of deduplicated.
For this reason I'm reporting this as a possible bug.

[infectormp]

Show us du -sh borg_folder/data

[ThomasWaldmann]

Also check if the repo is append-only.

[alfredonodo]

du -sh borg_folder/data
52G	borg_folder/data

The repository is configured as follow:
borg init --encryption=repokey-blake2 repository_path
and this is the only difference with the other machines:
borg init --encryption=repokey repository_path

[ThomasWaldmann]

-blake2 just changes how the MAC is computed. Rather unlikely that this influence space usage or related bugs.

[alfredonodo]

Right, but it is the only difference. Any idea about what to check?