Backup grows out of space #1847
Comments
|
Hello Osmandfan, Please notice that the version of BIT you are using is over 5 years old and from a time before the current maintenance team took over the project. But I am assuming that your current problem is independent from that version and would also arise with the latest version 1.5.2. How do you verified that files are not deleted? Can you show me the related shell commands and their output please. |
buhtz
added
the
Feedback
|
Thank you kindly for your quick reply. This is how I checked. I just looked up the file name in my back folder.
Strangely enough when you compare the 2 folders
|
|
About the difference in size between About your first screenshot: This doesn't help me much. That file Then please open a terminal/shell. Frist proof that the file is not present in the source: Show me the list of snapshots taken (the folders named like timestamps): Then show me where in this folders the deleted file still exists: You have to modify the pathes in this commands acordingly to your system. I don't see your full pathes in the screenshot. Let me show a real world example from my system. |
|
This is were the file was before These are the list of the snapshots This is the place on target were it still reside Hope this helps a bit more with the puzzle |
|
Please just copy the text from the terminal and paste it here in the GitHub "forum" as a code block. Don't make screenshots. Also please include the commands you used to create that output. |
|
Okay sorry. Do you want me to do that now or just next time I post something? |
|
After you deleted the zip file in your source folder. Did you modified anything else in your source? Did you deleted other files? And more important, did you modified other existing files? Or was it just deleting?
It is OK. Please post this command and its output. Hope there are no typos in it: |
|
Sorry forgot to answer your question. Yes I might have modified a few files in source but did not delete any other big files as far as I can remember, |
And can you verify that the modified files are correct backuped up? Sorry, I am still poking in the dark. But I assume this is a duplicate of the long standing bug #136 . After we joined the project ~3 years ago we are still not deep enough into the details of how BIT's behavior to give an answer to this issue. |
buhtz
added
Bug
and removed
Feedback
|
No need for sorry. I am very happy you are willing to look into this. Do I understand this might indeed be a bug? Overall I am happy with Backintime but gotta be sure it is doing 100%. I don't recall which files I modified. But I just tested it by modifying one file and checking it in the backup. It works fine. |
|
Yep, I would understand this as a bug. The reasons are lying in the complex behavior of rsync regarding to file permissions and how it determine modifications. |
So it seems to be a one time error for unknown reasons because my recent test went okay. |
This command did not work "backintime --diagnostics¨
My backup is growing to fast because it does not seem to delete the file in target that were deleted in source.
Is there a setting to do that? I just can't seem to find the answer anywhere.
I have back in time installed from standard linux mint repository.
Thank you for your help
The text was updated successfully, but these errors were encountered: