unpredictable behaviour

Dave Dykstra dwd at bell-labs.com
Tue Nov 6 07:58:35 EST 2001

On Fri, Nov 02, 2001 at 08:55:14AM -0800, tim.conway at philips.com wrote:
> I see very odd results from rsync 2.4.7pre1, the latest cvs version (sept 
> 12, i think was the last modified file).
> It's about 128Gb of data in about 2.8M files.
> Any idea what this randomness is?  might the "Value too large for defined 
> data type" be thrown if the system runs out of memory?  These jobs get up 
> to over a half a gig memory used.
> It was compiled (and is running) on a 64-bit machine.

I don't think it would get that message from running out of memory, although
a process size of >512MB of memory is awfully big.

The message "Value too large for defined data type" is what is printed for
an EOVERFLOW message, at least on Solaris 7.  What operating system are
you using?  It looks like all your messages all say "readlink" which is
printed in the function make_file() in flist.c after a failed call to
readlink_stat().  readlink_stat() calls do_lstat() in syscall.c, which
calls lstat64() if HAVE_OFF64_T is defined, otherwise it calls lstat().
Check your config.h to see if HAVE_OFF64_T is defined.  With that much data
I assume you've got large filesystems and you would need the 64 bit

rsync 2.4.7pre1 uses a relatively new autoconf rule for support of 64 bit
systems.  You didn't happen to regenerate the configure script with
autoconf, did you?  If you do, it has to be version 2.52 or later.

- Dave Dykstra

More information about the rsync mailing list