Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archive and repo sizes are wrong #2067

Open
2 tasks done
QuarkZ26 opened this issue Aug 30, 2024 · 6 comments
Open
2 tasks done

Archive and repo sizes are wrong #2067

QuarkZ26 opened this issue Aug 30, 2024 · 6 comments
Labels
status:duplicate Another identical issue has been posted

Comments

@QuarkZ26
Copy link

QuarkZ26 commented Aug 30, 2024

Description

Archive and repo sizes seem to often be completely off. For example, I have a repo in Borgbase, getting the info from borg command line returns:

Original size: 20.44GB
Compressed size: 14.64GB
Deduplicated size: 3.96GB

which is consistent with that I see on the site. Vorta on the other end shows:

Original Size: 20.4GB
Deduplicated size: 6.1
Compressed size: N/A (this literally never shows anything for me, doesn't matter if it's remote or local, it's always N/A)

Meanwhile, the reported sizes of each archive, I have 5 at the moment: 0.2GB, 0.2GB, 0.3GB, 0.3GB, 0.3GB

Trying the Recalculate option doesn't change anything. I have a local repo also, and all show 0.2GB, there are 9 archives, but the dedup size shows 9GB.

Any ideas as to why that is?

Reproduction

  • I tried to reproduce the issue.
  • I was able to reproduce the issue.

OS

Arch

Version of Vorta

0.9.1

What did you install Vorta with?

Distribution package

Version of Borg

1.4.0

Logs

No response

@m3nu
Copy link
Contributor

m3nu commented Aug 30, 2024

From what I remember, our numbers come from borg info. But the compressed number was removed because it can take a long time to calculate. The precise reason may be in a Github issue.

@QuarkZ26
Copy link
Author

The info I got above comes from borg info and yet the numbers don't match. Also it gives me the compressed number right away, so I'm not sure why that would be a problem, and really, shouldn't it be the user's choice whether to get that info or not? It seems that if you're going to have that in the UI, never retrieving it is just bizarre.

Also, it doesn't explain the archive numbers which are also completely off. I have another repo that has 20GB of data with the same discrepancy. I have 4 archives there, the first one being somehow 0.2MB, then two of 82MB and finally one of 1.2GB. Just got to wonder where those numbers are from? Clearly it doesn't add up, unless I'm missing something.

@m3nu
Copy link
Contributor

m3nu commented Aug 31, 2024

The number was removed for borg v2. So we removed it in Vorta.

There is a pending PR to add it back for borg v1 only, but the PR never got finished. If the timing issues can be solved for this PR, it's good to merge: #1751

@m3nu m3nu added the status:duplicate Another identical issue has been posted label Aug 31, 2024
@m3nu
Copy link
Contributor

m3nu commented Aug 31, 2024

Duplicate of #1750

@m3nu m3nu marked this as a duplicate of #1750 Aug 31, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the status:stale This item will be closed soon due to inactivity label Nov 30, 2024
@Satlinker
Copy link

Satlinker commented Dec 1, 2024

When I backup a many GB source for the first time, it shows about the right archive size.
When the second backup is done, the size of the first backup doesn' change -also ok.
When I recalculate both backups, both archive sizes are only a few kB. There must be something wrong?

@github-actions github-actions bot removed the status:stale This item will be closed soon due to inactivity label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:duplicate Another identical issue has been posted
Projects
None yet
Development

No branches or pull requests

3 participants