similar to: "Corrupt file" error messages

I've been having a problem for the past several days with a shellscript that has been working without problems for the 11 months. It's working until the comes up with the following error: total: matches=349 tag_hits=4061 false_alarms=1 data=6628073 ERROR: file corruption in public_html/reports/analog/analog.conf. File changed during transfer? I've tried deleting some of

hi! I have a problem with rsync (current CVS version), running on a win2k machine (rsync compiled using Cygwin). c:\rsync>rsync --version rsync version 2.4.6dev protocol version 24 Copyright (C) 1996-2001 by Andrew Tridgell, Paul Mackerras and others Capabilities: 64-bit files, socketpairs, hard links, symlinks It can DOWNload >2gb files from my linux box (with rsync reporting negative

Hello! I need to do rsync between local drives on win32. Rsync works, but it never ends. I started it with -vv and it writes something like: total: matches=0 tag_hits=0 false_alarms=0 data=0 And then it stays forever. :-( Could you help me?

Hi! I try to use batch mode to send only the difference between two packed CDs by email over a slow line. I create the diff with: rsync -avvv --write-batch=rs CD-ROM-V6.6.32.zip CD-ROM-V6.6.31.zip where alfred:/Auslieferung/CD # l -n -rw-r--r-- 1 0 0 453248121 Sep 2 16:22 CD-ROM-V6.6.31.zip -rw-r--r-- 1 0 0 407416499 Sep 29 13:39 CD-ROM-V6.6.32.zip resulting

Hello. I just started messing around with RSync to synchronize some RRD files between a couple BSD/Linux boxes. To test, I'm just trying to sync about 20 of these files which are about 256KB each. It seems that the full contents of each file are being transferred each time; i.e., the incremental transfer feature isn't working. I'm basing this assumption on output such as the

I'm having a problem with large files being rsync'd twice because of the checksum failing. The rsync appears to complete on the first pass, but then is done a second time (with second try successful). When some debug code was added to receiver.c, I saw that the checksum for the remote file & the temp file do not match on the first try, so (as expected) it repeats the rsync & the

Hi J.W. et al, Kevin Everets was kind enough to inform me about some strange behavior in his backup script, which seems to be the result of --link-dest behaving unexpectedly in the case where target/ is already populated with older versions of the same file. Here's the situation: We want to do: $ rsync -a --link-dest=../backup.1 source/ backup.0/ There is a file present under all three

I go thru this every few mnths it seems. Rsyncs exclude rules are very sophisticated but because of that somewhat unfathomable at times. Simplified: I want to exclude directories named no_bak anywhere in the tree but only the files under them, not the direcrories themselves. My exclude rules look like: no_bak/* /no_bak/* The first one does catch directories by that name on the first level but

The attached script file gives all the relevant details - I hope - please ask if you need any more information. /Sam Sam Sexton <mailto:sam.sexton@reuters.com> Reuters Coventry Automated Dealing Technologies Phone: +44 24 7625 6562 Fax: +44 24 7655 5203 -------------------------------------------------------------- -- Visit our Internet site at

https://bugzilla.samba.org/show_bug.cgi?id=2781 Summary: rsync linked files not listed as uptodate Product: rsync Version: 2.6.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: idallen@idallen.ca

https://bugzilla.samba.org/show_bug.cgi?id=1582 Summary: rsync dry run cannot find missing folders, contradicts actual run. Product: rsync Version: 2.6.2 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi All, I've seen several variations on this topic, but nothing exactly the same: I have two Windows 2003 servers that I want to use rsync (2.6.8) to mirror. These machines are separated by a WAN. Initial attempts to get rsync working between them have not been successful. The first rsync went fine, which seeded the files, but the second sync always fails (at a ramdom time) with a

Everything worked, files transferred fine however a -vvv reveals that the process did not end clean. The error is not seen with -v or even -vv. Any insight? rsync version 2.5.5 protocol version 26, running on Solaris 8. Write failed flushing stdout buffer. write stdout: Broken pipe rsync error: unexplained error (code 255) at main.c(925) _exit_cleanup(code=255, file=main.c, line=925): about to

Hi all. I'm sorry if this is a simple, obvious question, but I've looked around, and can not find an answer to this. What exactly are the false_alarms in the rsync summary? I am getting a number of false alarms in several of my rsync processes. Here's my output from one of my logfiles: total: matches=9724 tag_hits=741242 false_alarms=36 data=20850152 wrote 11731892 bytes read

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

I'm having a problem where my rsync processes don't exit. They finish their task.. but they don't exit. I'll see at the end, if i'm running -vv, something like: total: matches=727 tag_hits=771 false_alarms=0 data=2034655738 but the process continues to run, but not do anything apparent. If I strace the process, I see a ton of: select(0, NULL, NULL, NULL, {0, 1000}) = 0

Apologies for not including this info in the first place! My rsycn version is: rsync version 2.4.6 Copyright Andrew Tridgell and Paul Mackerras And my OS is: Red Hat Linux release 7.1 (Seawolf) Kernel 2.4.2-2 on an i686 --jessica On Fri, Nov 09, 2001 at 08:43:44PM -0800, Jessica Koeppel wrote: > > I'm having a problem where my rsync processes don't exit. > > They finish

Hi, I have a problem when running rsync over ssh. This might be a ssh problem, but i've only seen it with rsync so far. Every minute I rsync one file to 3 servers, and once in a while, there are stray processes laying around. Like this: Oct23 0:07 /usr/sbin/crond -l10 01:38 0:00 \_ /bin/sh -c /bin/sh cronjob-server-stats.sh minute 01:38 0:00 | \_ /bin/sh cronjob-server-stats.sh

Hi I am getting messages like total: matches=0 tag_hits=0 false_alarms=0 data=0 or total: matches=29 tag_hits=59 false_alarms=0 data=1663794 in STDERR when I use rsync with "-vv". Is this a known bug? Here is the full rsync command: rsync -e ssh -abvv --delete --exclude lost+found/ --exclude core --exclude *.o --exclude .netscape/cache --max-delete=250 --backup-dir=/some/path

Why does using --delete -b --backup-dir relative/path puts the deleted files in the target folder, while using the full path works as expected? my experimentation... root@feral:/tmp/test (0)>uname -a Linux feral 2.4.22-1.2115.nptlsmp #1 SMP Wed Oct 29 15:30:09 EST 2003 i686 i686 i386 GNU/Linux root@feral:/tmp/test (0)>rsync --version rsync version 2.5.6 protocol version 26