On Tue, Jul 10, 2001 at 04:13:11PM -0700, Jos Backus wrote:
> I'm using the same CVS server. I think my problem is that I applied your
> rsync-nohang.patch first, whereas I should only be applying
> rsync-nohang2.patch against the current CVS sources. Correct?
To answer my own question: yes. rsyn
On Tue, Jul 10, 2001 at 03:19:51PM -0700, Wayne Davison wrote:
> They will apply to stock 2.4.6 with offsets (but no fuzz), if you so
> desire. They were created from the CVS version, though.
OK.
> The nohang1 patch is already incorporated into the CVS version, so it is
> the only one that sho
On Tue, 10 Jul 2001, Jos Backus wrote:
> On Tue, Jul 10, 2001 at 01:59:22PM -0700, Wayne Davison wrote:
> > http://www.clari.net/~wayne/rsync-nohang1.patch
> > http://www.clari.net/~wayne/rsync-nohang2.patch
>
> Are these to be applied against the stock 2.4.6?
They will apply to stock 2.4
"A month of sundays ago Steve Ladendorf wrote:"
> variety of conditions, one of which I seem to be having. We use rsync to
> update remote servers over night. Each system syncs with a master server
> holding around 4.0 gig of data. Normally there is very little change on
> the master so rsync o
Hi Wayne,
On Tue, Jul 10, 2001 at 01:59:22PM -0700, Wayne Davison wrote:
> http://www.clari.net/~wayne/rsync-nohang1.patch
> http://www.clari.net/~wayne/rsync-nohang2.patch
Are these to be applied against the stock 2.4.6? In particular, the second
patch does not apply cleanly against
On Tue, 10 Jul 2001, Steve Ladendorf wrote:
> Is there something I'm doing wrong? What can I do to prevent rsync from
> hanging all the time??
If you avoid using -v, that can help rsync not to hang. However, a
better fix is to apply this patch:
http://www.clari.net/~wayne/rsync-nohang1.pat
There are 2 patches on this mailing list that fix the 2.4.6 hangs for
me. Check the archives and you should be able to find them.
I hope to see a 2.4.7 out soon that includes some or all of those hang
fixes.
eric
Steve Ladendorf wrote:
>
> I see there is quite a bit discussion on the list abo
I see there is quite a bit discussion on the list about rsync hanging on a
variety of conditions, one of which I seem to be having. We use rsync to
update remote servers over night. Each system syncs with a master server
holding around 4.0 gig of data. Normally there is very little change on
th
Dave> Try using "-W" to disable the rsync rolling checksum algorithm
Dave> when copying between two NFS mounts, because that causes extra
Dave> NFS traffic. Rsync's algorithm is optimized for minimizing
Dave> network traffic between its two halves at the expense of extra
Dave> local access and i
On Wed, Jan 24, 2001 at 03:48:06PM -0500, John Stoffel wrote:
...
> or it doesn't have a good heuristic that says:
>
> if I don't get *any* info after X seconds, just die
>
> where X would be something like 900 or 1200 seconds, which seems like
> a reasonable number.
Have you tried --timeou
Quick follow to my previous posting today.
I'm now using the -W flag on 2.4.6 again and it just hung. Luckily a
'kill -HUP' to the process it's waiting on will do the trick in terms
of killing rsync cleaning. But it also means I have to sit and watch
the damm thing do it's work and wait until
Dave> Other people have reported similar experiences but nobody has
Dave> pointed to a problem in rsync; the problem is more likely to be
Dave> in NFS on the NetApp or Solaris machines. I believe most NFS
Dave> traffic goes over UDP but do you happen to know if it using TCP?
Dave> We have seen m
On Wed, Jan 24, 2001 at 11:59:18AM -0500, John Stoffel wrote:
>
>
> Hi all,
>
> This is a followup to bug report 2779 on the rsync bug tracking web
> site, I'm also seeing the hang in waitid() on the master process when
> trying to do an rsync on a single host.
> Thanks,
> John
>John St
On Wed, Jan 24, 2001 at 11:59:18AM -0500, John Stoffel wrote:
>
>
> Hi all,
>
> This is a followup to bug report 2779 on the rsync bug tracking web
> site, I'm also seeing the hang in waitid() on the master process when
> trying to do an rsync on a single host.
>
> Basically, I've got a server
Hi all,
This is a followup to bug report 2779 on the rsync bug tracking web
site, I'm also seeing the hang in waitid() on the master process when
trying to do an rsync on a single host.
Basically, I've got a server with two network interfaces, connected to
two different NetApps and I'm using r
15 matches
Mail list logo
