DO NOT REPLY [Bug 5963] New: rsync fails with errors that make no sense...

[samba-bugs at samba.org]

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

           Summary: rsync fails with errors that make no sense...
           Product: rsync
           Version: 3.0.4
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: crhea at mayo.edu
         QAContact: rsync-qa at samba.org


CentOS 5.2 / x86_64 / download+build of rsync 3.0.4.

Transferring data between two NetApp servers-- both NFS mounted on this (Linux)
system. We're transferring from one directory tree to another with a script
that looks like:

for i in /data2/* /data3/*
do
        /usr/local/bin/rsync -a --delete ${i}/ /data1/`basename $i`
done

For some files/dirs, rsync is failing:

rsync: rename "/data1/bordner/Pfam/version_22.0/fasta/.PF09720.fa.8z0Imb" ->
"Pfam/version_22.0/fasta/PF09720.fa": File too large (27)
rsync: rename "/data1/bordner/Pfam/version_22.0/fasta/.PF09721.fa.0OoTTG" ->
"Pfam/version_22.0/fasta/PF09721.fa": File too large (27)
rsync: rename "/data1/bordner/Pfam/version_22.0/fasta/.PF09722.fa.83Sssc" ->
"Pfam/version_22.0/fasta/PF09722.fa": File too large (27)
rsync: rename "/data1/bordner/Pfam/version_22.0/fasta/.PF09723.fa.0ynM2H" ->
"Pfam/version_22.0/fasta/PF09723.fa": File too large (27)
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1040) [sender=3.0.4]

The individual files are NOT "too large":

[root at rcfcluster-rsync fasta]# cd /data3/bordner/Pfam/version_22.0/fasta/
[root at rcfcluster-rsync fasta]# ls -l PF09723.fa
-rw-rw-r-- 1 m049922 bordner 21279 May 22  2008 PF09723.fa

BUT, the directory is very large:

[root at rcfcluster-rsync fasta]# ls -1 | wc -l
191811


-- 
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.