Thanks Mike,
I tried your patch and actually had created something similar myself right
before you replied, but made sure to try your patch as well, since my
python skills are at best rudimentary.
Anyhow, both modifications lead to the result that apparently the size
doesn't match. Over the last few days the number of affected files has
increased to 52, even though the "new" four files with this error also
haven't changed in months.
Anyhow when I copy these files from the source by hand (using the "cp"
command in my shell), the size matches. Also a curious other observation
is that starting from the second error the size attribute of the first
argument is always identical to the size attribute of the second argument
of the previous error. Its too weird to be a coincident. The files
affected are not in the same directories nor seem to have many other
connections, other than being ascii files of the same format and
extension (but so are the other 9000)....
Is there a patch that the tmp file will NOT be deleted in case an error
occurs? I believe taking a look at these files will be quite instructive.
Thanks,
Thomas
On Thu, 29 May 2014, Mike Fleetwood
wrote:
On 29 May 2014 17:14, Thomas Witzel <[email protected]> wrote:
Hello,
I hope this is not duplicate from a previous issue, but I couldn't find my
exact scenario.
I'm using rdiff-backup 1.2.8 on an unbuntu machine and everything is working
great except that for one of my nightly backups 43 of 9101 files are always
missing. If there was no changes my statistics looks like this:
StartTime 1401379711.00 (Thu May 29 12:08:31 2014)
EndTime 1401379724.83 (Thu May 29 12:08:44 2014)
ElapsedTime 13.83 (13.83 seconds)
SourceFiles 9101
SourceFileSize 335423184 (320 MB)
MirrorFiles 9101
MirrorFileSize 335423184 (320 MB)
NewFiles 0
NewFileSize 0 (0 bytes)
DeletedFiles 0
DeletedFileSize 0 (0 bytes)
ChangedFiles 43
ChangedSourceSize 0 (0 bytes)
ChangedMirrorSize 0 (0 bytes)
IncrementFiles 43
IncrementFileSize 0 (0 bytes)
TotalDestinationSizeChange 0 (0 bytes)
Errors 0
So there is always 43 IncrementFiles, but those files are missing from the
backup and for those 43 files I get messages lile this:
UpdateError xxx.txt Updated mirror temp file /xxxx/rdiff-backup.tmp.77 does
not match source
I have no idea what mismatch this is referring too. I can manually copy the
source to rdiff-backup.tmp.77 and with no tools at my disposal can I find a
difference. I also can't see whats different about those 43 files from the
other 9000, they are all very similar with similar names. Of the 43 affected
files the most recent change occured 9 months ago in one of them, so its not
that they changed during the backup. How do I go about debugging this ?
Thank you,
Thomas Witzel
Hi Thomas,
Try temporarily applying the attached patch and running rdiff-backup
with -v 7 or greater. It will log why rdiff-backup decided the file
changed during the backup.
Thanks,
Mike
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
_______________________________________________
rdiff-backup-users mailing list at [email protected]
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
