Backup : difference sizes between yunohost admin, console, sftp


I noticed something “space” (strange) about the management of archives
If I look at the size of my backup via yonohost web admin, for the same archive, it does not correspond to those of a console or data via sftp.
Via the yunohost web client, the archive is 883 Mb

Via the console it makes 447M

/home/yunohost.backup/archives$ ls -lah
total 447M
drwxr-x--- 2 admin root 4.0K Jul 21 16:22 .
drwxr-xr-x 4 root  root 4.0K Jun 26 22:53 ..
-rw-r--r-- 1 root  root 2.3K Jul 21 16:18
-rw-r--r-- 1 root  root 447M Jul 21 16:18 20190721-141630.tar.gz

And via sftp, it is 467.7Mo

I would say that the console is right, but …
Why this difference


J’ai remarqué une chose bizarre au niveau de la gestion des archives
Si je regarde la taile de mon backup, pour une même archive, elle ne correspond pas à celles d’une console ou des données via sftp.
Via le client web yunohost, l’archive fait 883 Mb
Via la console elle fait 447M
Et via sftp, elle fait 467,7Mo (cf image)

Pourquoi cette différence ?
Je dirais que c’est la console qui a raison, mais bon…

I don’t know about the size of the archive via the web interface.

But for the ones via the console and sftp, it is most probably because the console is using a binary prefix and the sftp client is using a SI prefix (metric).

467,7MB * 1000^2 / 1024^2 = 446,033MiB

MB is megabyte and MiB mebibyte.

Source :

Both are right : the console size / file explorer size shows the compressed size whereas the admin shows the uncompressed size (which you may see inside the info.json)

Maybe the admin should find a more explicit way to display this tho (in fact both infos are relevant to know probably…)


thank you for the clarification
It’s true that this is not explicit the web admin panel data :wink:
Maybe to put the 2 values ​​would be more readable;)

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.