Hi, I've wanted to start working with this CVS version cuz the new "incremental-recursion algorithm" is just what I need. But ran into a problem... When I start the rsync, either with the rsync protocol or rsh, i found that it'll start doing the rsync and just halt after a few hundred MBs or even up to a couple GBs. I was never able to finish an rsync. Anyone else had this problem? Shai -------------- next part -------------- HTML attachment scrubbed and removed
On 1/21/07, Shai <shaibn@gmail.com> wrote:> I've wanted to start working with this CVS version cuz the new > "incremental-recursion algorithm" is just what I need. But ran into a > problem... > > When I start the rsync, either with the rsync protocol or rsh, i found that > it'll start doing the rsync and just halt after a few hundred MBs or even up > to a couple GBs. > > I was never able to finish an rsync. > > Anyone else had this problem?I had a similar problem, and Wayne is in the process of fixing it. Right now he's waiting for me to provide backtraces for the hung processes, which I will do very soon. See this thread: http://lists.samba.org/archive/rsync/2007-January/017080.html Matt
On Sun, Jan 21, 2007 at 08:43:56AM +0200, Shai wrote:> When I start the rsync, either with the rsync protocol or rsh, i found > that it'll start doing the rsync and just halt after a few hundred MBs > or even up to a couple GBs.I had not encountered this hang until today. The backtrace implicated a problem in the wait_for_receiver() routine, and I figured out that every now and then the io_flush() call could end up reading the last available message from the receiver, giving the read_msg_fd() call nothing to read (causing a deadlock). I checked in a fix for this and released a new "nightly" tar file. Thanks for your help in testing rsync! ..wayne..