You're the third person I've heard about lately saying they saw nulls in
files copied by rsync, but the first on such an old version. What are the
operating systems of the NFS client and server? The case I heard about
before was a solaris client and sunos4 server and I suspected it was a
problem with NFS. To recover from the situation you can add a --checksum
option so rsync will detect the corrupted files; otherwise it skips over
those that it has previously copied and have matching timestamps & sizes.
By the way, rsync is designed to work most efficiently when it operates on
local disks, so if you can run rsync on the NFS server you'll probably be
better off. When going over NFS as you are, it appears to rsync as if
it is a local disk-to-disk copy and the most recent versions automatically
add a --whole-file option to disable the rsync rolling checksum algorithm.
- Dave Dykstra
On Thu, May 16, 2002 at 10:51:35PM -0700, girish adiga
wrote:> Hi All,
> I am using rsync version 2.4.5 protocol version 24
>
> Some times the file size will be zero or the file
> contains NULLs when used rsync. ?
>
> The command i have used pasted below.
>
> I want to sync file c to my local m/c.
>
> cd /net/a/
> for file in `ls */c`
> rsync -rR --delete $file <Local Dir Path>
> done
>
> This is run every 1 hr using cron job to update file c
> in local directory.
>
> Is there anything wrong in command.
>
> Any help would be greatly appreciated.
>
> Thanks,
> Girish
>
> __________________________________________________
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
> http://launch.yahoo.com
>
> --
> To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html