Block of unwanted zeros in a dest file

[Dave Dykstra]

Eric, which version of Sun operating system were you running, and was there
any NFS involved?  What's a NAS disk?  I had a user who reported having
rsync (a CVS version between 2.5.4 and 2.5.5) produce a file filled with
nulls but he was copying from a Solaris client which was mounting over NFS
from a Sunos4 server, and the files were not readable because he was
running as root on the Solaris client and the filesystem was not exported
from the Sunos4 server to allow root access.  The problem went away when he
used another operating system.  We speculated it may have been that the
Sunos4 NFS implementation wasn't returning the proper error code.

I haven't seen anbody else report problems with rsync producing files of
nulls, but it's pretty disconcerting.

- Dave Dykstra


On Mon, Mar 25, 2002 at 12:28:06PM -0700, Eric Whiting wrote:
> I'm syncing from a linux box (NAS disk) to a sun (NAS disk).
> 
> I just found a file on the destination sun with zeros from bytes 8192 to
> 32767. (the source file had lots of 'good' random bytes). The rest of
> the file compares properly. Repeatedly running rsync to send the file
> didn't fix it. I ran a -c transfer (checksum) and it fixed the file.
> 
> I'm using 2.5.3 on both sides with the -z turned off. (I thought that
> was somewhat 'safe')
> 
> Is this a know issue? I'll upgrade to 2.5.4 (with the fixed zlib) and
> see if it acts the same.
> 
> eric