← Back to team overview

duplicity-team team mailing list archive

Re: [Question #674425]: rsync backend Remote filesize 0 does not match local size N, retrying

 

On 26.09.2018 02:07, BenRifkah Bergsten-Buret wrote:
> New question #674425 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/674425
> 
> I'm trying to get backups running from my CentOS server to a RHEL remote server. I keep getting this error when I try to back up:
> 
> "Remote filesize 0 for 'duplicity-full.20180925T231400Z.vol1.difftar.gz' does not match local size 496, retrying."
> 
> It appears  5 times and then duplicity gives up. When I check the files on the remote server they have a non-zero size. It looks like the rsync backend is having trouble checking and reporting the size. I have a minimum example that produces the message but syncs to a different directory on the source host.
> 
> Here's the info level log output:
> 
> "$ duplicity full --no-encryption pkgs rsync://localhost//home/CHSCC/bburnett/duplicity_backup_test/pkgs/
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: none
> Remote filesize 0 for 'duplicity-full.20180926T000202Z.vol1.difftar.gz' does not match local size 496, retrying.
> Remote filesize 0 for 'duplicity-full.20180926T000202Z.vol1.difftar.gz' does not match local size 496, retrying.
> Remote filesize 0 for 'duplicity-full.20180926T000202Z.vol1.difftar.gz' does not match local size 496, retrying.
> Remote filesize 0 for 'duplicity-full.20180926T000202Z.vol1.difftar.gz' does not match local size 496, retrying.
> Remote filesize 0 for 'duplicity-full.20180926T000202Z.vol1.difftar.gz' does not match local size 496, retrying.
> --------------[ Backup Statistics ]--------------
> StartTime 1537920123.57 (Tue Sep 25 17:02:03 2018)
> EndTime 1537920123.61 (Tue Sep 25 17:02:03 2018)
> ElapsedTime 0.03 (0.03 seconds)
> SourceFiles 29
> SourceFileSize 86 (86 bytes)
> NewFiles 29
> NewFileSize 86 (86 bytes)
> DeletedFiles 0
> ChangedFiles 0
> ChangedFileSize 0 (0 bytes)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 29
> RawDeltaSize 0 (0 bytes)
> TotalDestinationSizeChange 496 (496 bytes)
> Errors 0
> -------------------------------------------------
> 
> bburnett@chrusm0:~$ ssh localhost ls -lG duplicity_backup_test/pkgs/ 2>/dev/null                                     total 5
> -rw-------. 1 bburnett 193 Sep 25 17:02 duplicity-full.20180926T000202Z.manifest
> -rw-------. 1 bburnett 496 Sep 25 17:02 duplicity-full.20180926T000202Z.vol1.difftar.gz
> -rw-------. 1 bburnett 509 Sep 25 17:02 duplicity-full-signatures.20180926T000202Z.sigtar.gz
> $ duplicity --version
> duplicity 0.7.18.1
> $ lsb_release -a
> LSB Version:    :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:lan
> guages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
> Distributor ID: CentOS
> Description:    CentOS Linux release 7.5.1804 (Core)
> Release:        7.5.1804
> Codename:       Core"
> 
> (SSH Auth is being handled by an agent)
> 
> I don't have this problem when I try the same rsync-to-localhost using Ubuntu on Windows 10 with duplicity 0.7.17. Has anyone seen this before?
> 

hey Ben,

nope, at least this never came up on the list until now. rsync backend does not support reporting file sizes, so this error should never occur.

1.
what is your duplicity version?

2.
please run the backup with max. verbosity '-v9' and put the _full_ terminal output on a filehoster/pastebin or such and post the link. somewhere view/downloadable. obfuscate private strings in it beforehand if needed.

..ede/duply.net


Follow ups

References