crash on 2 gig file

jw schultz jw at
Mon Jun 16 15:14:58 EST 2003

On Mon, Jun 16, 2003 at 12:10:03AM -0400, Brian K. White wrote:
> Tomasz Ciolek wrote:
> >>>On Wed, Jun 11, 2003 at 04:16:38PM -0400, Brian K. White wrote:
> >>>
> >>>>...
> >>>>2.5.6 (protocol 26) from cvs on SCO Open Server 5.0.6
> >>>>both machines are the same version of OS and the same copy of rsync.
> >>>>...
> >>>>file on LIVE is 0 bytes
> >>>>file on BACKUP is 2 gigs
> >>>>
> >>>>on BACKUP you run:
> >>>> rsync -az --delete LIVE:/u/appl /u
> >>>>
> >>>>causes all files in the list before the 2gig file to update, nothing
> >>
> >>else.
> >>
> >>>Does SCO support files over 2GB in size?
> >>>
> >>>-- 
> >>>Tomasz M. Ciolek
> >>
> >>Nope.
> >>
> I can imagine that dealing with a file that reaches the OS's maximum file 
> size limit is problematic. No surprize there. The point of the report was 
> that, don't you think rsync should deal with this situation in a better 
> way than crashing and thus failing to do the rest of the job it was in the 
> middle of?
> Call me ignorant, but it seems to me rsync should be able to deal with any 
> file that the OS can deal with, including one that is exactly as large as 
> it is possible for a file to get. I would not put the mere existance of 2 
> gig files in the same "don't do that" category as say, not having any free 
> space for temp, not having any swap, trying to deal with large file lists 
> and large files without lots of ram etc...

I agree within the limits of reasonable code.  But you don't
provide any diagnostic info, patch, or test case that works
on something even one rsync developer has so we have little
choice but to ignore this as a rare problem on only one
obsolete OS :>

	J.W. Schultz            Pegasystems Technologies
	email address:		jw at

		Remember Cernan and Schmitt

More information about the rsync mailing list