rsync - Apr 2010 - DO NOT REPLY [Bug 7380] New: rsync not backing up certain binaries

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

           Summary: rsync not backing up certain binaries
           Product: rsync
           Version: 2.5.7
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: enslaver at enslaver.com
         QAContact: rsync-qa at samba.org


I am rsyncing directories from one system to the other for nightly backups, I
have noticed it refuses to copy some binaries even though they have different
sizes, dates and checksum, i even tried with the -c option. The file
"runcbl"
is the one that is different.

Here is what is happening:
[root at inqdbvm RWzzz]# /usr/bin/rsync -aucvx --rsh="ssh" --delete
aries3:/RWzzz
/Backup/aries3
root at aries3's password: 
receiving file list ... done
RWzzz/AP01/APFAUX01.DAT
RWzzz/AP01/APNOTF01.DAT
RWzzz/AP01/APRCUR01.DAT
RWzzz/AP01/PCOFIL01.DAT
RWzzz/AP01/VENFIL01.DAT
RWzzz/RWWRK/
RWzzz/AR02/CUSFIL02.DAT
RWzzz/AR02/CUSFIL02.vix
wrote 56072 bytes  read 218126 bytes  4853.06 bytes/sec
total size is 2212191051  speedup is 8067.86

[root at inqdbvm RWzzz]# ls -la /Backup/aries3/RWzzz/runcbl
-rwxrwxrwx    1 root     root      1647880 Oct 15  2008
/Backup/aries3/RWzzz/runcbl

[root at aries3 RWzzz]# ls -la /RWzzz/runcbl
-rwxrwxrwx    1 root     root      2205724 Jul 21  2008 /RWzzz/runcbl

[root at inqdbvm RWzzz]# file runcbl
runcbl: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux
2.2.5, dynamically linked (uses shared libs), stripped


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

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





------- Comment #1 from matt at mattmccutchen.net  2010-04-21 12:17 CST -------
Rsync 2.5.7 is six years old; we won't support it.  If you're using an
"enterprise" OS distribution, you can ask the vendor.  Otherwise,
please
upgrade rsync.


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

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





------- Comment #2 from enslaver at enslaver.com  2010-04-21 12:27 CST -------
Attempted in 3.0.7, same issue.


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

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


matt at mattmccutchen.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Comment #3 from matt at mattmccutchen.net  2010-04-21 12:34 CST -------
Ah.  You are using the -u option, which tells rsync not to replace the newer
destination file with the older source file.  If that's not what you want,
remove the -u option.


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

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





------- Comment #4 from enslaver at enslaver.com  2010-04-21 12:40 CST -------
Thanks, I saw that just now, I'm unsure how the backup file got modified to
be
newer than the one running but that solved it!


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