similar to: [Bug 8315] New: hang in rsync (match.c)

Hi - I'm using rsync 3.0.8 on Fedora 14 x86-64 (package, not built). I get a repeated crash trying to rsync to a particular zfs partition: [root at xback1 diskbackup]# rsync -raHx --inplace --numeric-ids --stats --no- whole-file --delete /xback1_back1/home_jss/20110225-000501/ /xback1_test1/home_jss/current/ Segmentation fault [root at xback1 diskbackup]# rsync: writefd_unbuffered failed to

Hi, I am running mentioned rsync version in daemon mode on a x86 machine which is a Gentoo Linux running kernel 2.4.26 and glibc 2.3.3_pre20040207. During the sync from another machine, the rsync daemon hangs; client receives no data and server waits on select() call. when this happens, rsync server process can only be killed by SIGKILL; no timeout occurs on server side. ssh is not being used for

https://bugzilla.samba.org/show_bug.cgi?id=10518 Summary: rsync hangs (100% cpu) Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: syzop at vulnscan.org QAContact:

I am trying to understand how match.c works. I am reading the code and something doesnt look quite right. This is usually a sign that I am missing something obvious. Here is what I see. build_hash_table uses qsort to order targets in ascending order of //tag,index// into the array of checksums. It then accesses the targets in ascending order and writes the index at the tag's location in

Hi, I'm experiencing timeouts during synchronization of large files. The scenario is as follows: Locally I have a large file (e.g. 20GB), which is already present at the server. When I try to resync it with: rsync --inplace --ignore-times -vvvv --compress bigfile rsync://xxx at ... The '--ignore-times' is only to force a comparison. The real world scenario would be the sync of a

Please find the attached patch which replace unsafe strcpy(3) by strncpy(3) functions. regards, Eduardo Silva

Greetings, I'd like to propose a new option to rsync, which causes it to read device files as if they were regular files. This includes pipes, character devices and block devices (I'm not sure about sockets). The main motivation is cases where you need to synchronize a large amount of data that is not available as regular files, as in the following scenarios: * Keep a copy of a block

Under cygwin 1.5.25 we get the following compile warnings flist.c: In function `output_flist': flist.c:2648: warning: unsigned int format, uint32_t arg (arg 4) flist.c:2648: warning: unsigned int format, uint32_t arg (arg 4) flist.c:2655: warning: unsigned int format, uint32_t arg (arg 5) flist.c:2655: warning: unsigned int format, uint32_t arg (arg 5) flist.c:2659: warning: int format,

There are quite a few compilation warnings from rsync-2.5.5rc1 that could be eliminated by code cleanup. gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o main.c: In function `start_client': main.c:665: warning: unused variable `write_batch' main.c:664: warning: unused variable `whole_file' These warnings will go away when the two variables are properly bracketed

Hi - I'm trying to diagnose a slow rsync problem. I'm trying to rsync a lot of fresh data between two systems with gigabit ethernet, but using ssh. The systems have large RAID disks, with pretty fast read and write benchmarks (>100MB/s). Both systems are running Fedora 10 Linux. I only get around 15MB/s transferred between the two systems using: rsync -raxSH --numeric-ids /indir

Hi, I recently came across a situation where "rsync --inplace" performs very poorly. If both the source and destination files contain long sequences of identical blocks, but not necessarily in the same location, the sender can spend an inordinate amount of CPU time finding matching blocks. In my case, I came across this problem while backing up multi-hundred-gigabyte MySQL database

Greetings! I loose all my metadata after concatenating corpora. This is an example of what happens: > meta(corpus.1) MetaID cid fid selfirst selend fname 1 0 1 11 2169 2518 WCPD-2001-01-29-Pg217.scrb 2 0 1 14 9189 9702 WCPD-2003-01-13-Pg39.scrb 3 0 1 14 2109 2577 WCPD-2003-01-13-Pg39.scrb .... .... 17 0

I just picked up rsync 2.5.6 and installed it. I haven't actually _used_ it for anything yet; this is entirely about a handful of minor issues I noticed while building it. You may care or you may not; for simplicity of language (to avoid many repeated "in case you care" and such), the text below is written assuming you care about them all. On a (32-bit) SPARC system, I noticed:

Attached is a patch that makes window strides constant when files are walked with a constant block size. In these cases, it completely avoids all memmoves. In my simple local test of rsyncing 57MB of 10 local files, memmoved bytes went from 18MB to zero. I haven't tested this for a big variety of file cases. I think that this will always reduce the memmoves involved with walking a large

Hello, A collegue of mine has compared the runtime of a linear model + anova in SAS and S+. He got the same results, but SAS took a bit more than a minute whereas S+ took 17 minutes. I've tried it in R (1.9.0) and it took 15 min. Neither machine run out of memory, and I assume that all machines have similar hardware, but the S+ and SAS machines are on windows whereas the R machine is Redhat

Hi all, The decoder is down 30% execution time, identical bit output. Didn't get the mdct yet; 1024 point mdct is a bit much to brute-force, and I'm not going to hand-unroll the whole thing either (the machine- unrolled version produced a 1.5M executable; understandably, it wasn't very fast. Still waiting for processors with 1.5M L1 code caches ;-) Slowest parts now are: -- mdct --

Hi I am trying to compile rsync-2.5.5 on Tru64 UNIX V5.1A The configure completed sucessfully however the make failed. The following is a copy of the configure and make output. Could you please provide advice as to why this is failing and hopefully resolution. Just as a matter of comparison - rsync-2.5.4 make also fails, however, rsync-2.4.8 compiled sucessfully on this version of Tru64 5.1A

This is to let you know that although rsync compiled on MacOSX 10.2.2, it failed certain tests. I have attached two files: (1) The combined output of "./configure" and make", and (2) the output of "make check". Please let me know if you need any further information. Ed ------------------------------------------------------- Edward N. Zalta

Hello all, Thanks for all the ideas. I liked the remote to remote idea and have told my guide about it. Anyways, can anybody tell me which files to look into, if I want to look at the code for file reconstruction. I have studied Dr. Tridgell's thesis on the Rsync Algorithm and have understood the working of the algorithm. Now, I am trying to read the code to understand it better. Any help

Hello, I m using asterisk version 1.6.2.0 beta. I m trying to test load on it, for which i m using WINSIP installed at two computers and facing two problems. Problem 1: I got 100 users registered to asterisk from each winsip and then initiates 100 calls from one winsip other winsip. But the problem is approx of 60 calls get mature and asterisk give error for the remaining like shown below.