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
restic diff says 16777215.998 TiB added/removed. #2469
Labels
Comments
rawtaz
added a commit
to rawtaz/restic
that referenced
this issue
Nov 22, 2019
rawtaz
added a commit
to rawtaz/restic
that referenced
this issue
Nov 22, 2019
rawtaz
added a commit
to rawtaz/restic
that referenced
this issue
Nov 22, 2019
7 tasks
rawtaz
added
the
state: need feedback
waiting for feedback, e.g. from the submitter
label
Nov 22, 2019
Great catch, thanks for the report! |
Thank you for writing the patch. I built it and check whether restic works as expected. It works great!
|
@trrk Thanks you, appreciate it. |
rawtaz
added a commit
that referenced
this issue
Nov 23, 2019
diff: Fix wrong bytes reported in diff stats (#2469)
seqizz
pushed a commit
to seqizz/restic
that referenced
this issue
Jan 22, 2020
seqizz
pushed a commit
to seqizz/restic
that referenced
this issue
Jan 30, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Output of
restic version
How did you run restic exactly?
Run on Raspberry Pi 2.
What backend/server/service did you use to store the repository?
rclone:local
Expected behavior
This output is from the same command run on Windows 7.
Actual behavior
Restic reports wrong added/removed size.
Steps to reproduce the behavior
I think it will be reproduced when run diff between snapshots which added or removed 2 GB or more.
Do you have any idea what may have caused this?
Integer overflow?
Do you have an idea how to solve the issue?
It seems that 16777215.998 TiB had been displayed on the other issue. #1954
I think the cause is the same as it.
Did restic help you or made you happy in any way?
I use restic for backup of music data. I'm happy with taking snapshots and deduplication.
The text was updated successfully, but these errors were encountered: