On 8/14/2010 3:09 AM, Matt McCutchen wrote:
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
I have sample data that exposes this repeatably:
http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed i
On Fri, 2010-08-13 at 11:26 -0400, Brian K. White wrote:
> I have sample data that exposes this repeatably:
> http://lists.samba.org/archive/rsync/2008-October/021889.html
Thanks, but we figured out the problem several months ago and it should
be fixed in rsync 3.0.7:
https://lists.samba.org/arch
On Thu, 2008-10-09 at 07:54 -0700, Wayne Davison wrote:
> I wonder if there was a false checksum
> match in the file? In such a case, the sender and the receiver would
> compress different "matching" data, and could potentially get out of
> sync.
That would explain it.
> If so, I doubt there's a
On Mon, Oct 06, 2008 at 11:28:31PM +0200, Bas van Schaik wrote:
> Since this is a production environment I'd like to stick to 3.0.3
> (which is already newer than I'd like to use...) in stead of upgrading
> to 3.0.4, unless have very good reasons to believe it is really fixed
> in that last version
Paul Slootman wrote:
> On Fri 05 Sep 2008, Bas van Schaik wrote:
>
>>> Well, why not try upgrading to the latest? If that's not an option for
>>> you, what do you want us to do? Retro-actively fix your version by
>>> jumping in our time machine? ;-)
>>>
>>>
>> You're right, I should ha
On Fri 05 Sep 2008, Bas van Schaik wrote:
> >
> > Well, why not try upgrading to the latest? If that's not an option for
> > you, what do you want us to do? Retro-actively fix your version by
> > jumping in our time machine? ;-)
> >
> You're right, I should have been more clear about this. I thi
Paul Slootman wrote:
> On Fri 05 Sep 2008, Bas van Schaik wrote:
>
>
>> is disabling the compression... FYI: both client and server are using
>> rsync 2.6.9 (from Ubuntu Hardy Heron). Does anyone have more information
>> regarding this issue?
>>
>
> Well, why not try upgrading to the latest
On Fri 05 Sep 2008, Bas van Schaik wrote:
> is disabling the compression... FYI: both client and server are using
> rsync 2.6.9 (from Ubuntu Hardy Heron). Does anyone have more information
> regarding this issue?
Well, why not try upgrading to the latest? If that's not an option for
you, what do
Hi all,
A little less than a year ago I replied to this thread, but I'm still
having similar problems. Again, the "Inflate (token) returned -5" error
occurred while syncing a file:
> 2008/09/04 22:11:20 [7017] name lookup failed for 172.26.3.224: Name
> or service not known
> 2008/09/04 22:11:20 [
