[Bug 10545] New: Rsync first time deletes files, second time it synchronates files with same name

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=10545

           Summary: Rsync first time deletes files, second time it
                    synchronates files with same name
           Product: rsync
           Version: 3.0.9
          Platform: x64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: e.d.grootjans at hccnet.nl
         QAContact: rsync-qa at samba.org


I have debian 7 X64 latest installed on my box.
Running rsync 3.0.9.
On both boxes the same versions.
I have an box with ip 192.168.0.6 on
which i make a daily backup

Daily backups are made in the directory /var/disk/disk-20/backup/daily
The mounting point of the disk is disk-20
Disk-20 is a 3 Tb Harddisk
It has a directory backup with 2 sub-dirs; one is daily, one is month.
Every first Monday of the month the fullbackup from Sunday is moved from daily
to month.

The backup is copied to another host with rsync.
I use the command:

su - rsync -c "/usr/bin/rsync -avh --delete --progress /var/disk/disk-20/
--exclude={lost+found} rsync:192.168.0.5:/var/disk-01 >/$logpath/rsync.log"

(disk-01 is a partition 2 of 146 Gb on a 200Gb Harddisk; partition 1 is Debian)

I noticid that synchronizing on Monday was just a few minutes,
but on thuesday it took about 26 minutes.
I found out that on thuesday it took so long because the file in month was
synchronised. This should be done on monday.
So on Monday after move of the full backup from daily to month the file in
daily was deleted.
And on thuesday month was synchronized.

Has this something to do with the fact that the names of the files are the
same.
(BACKUP-x-full-2014-04-06.tgz


If there is any information you need, please let me know.

Erik

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.