On Thu, Apr 08, 2004 at 02:42:10PM -0700, Wayne Davison wrote:
> To fix this will require a protocol change.
Since the 2.6.1 version that will be coming out soon has several
protocol improvements in the new protocol-28 (including one relating to
rdev-sending), it seems like this would be a good ti
er to compile 32bit until I see a fix go through for
this one.
Thanks for your help :)
Tom Williams
-Original Message-
From: Wayne Davison
To: Williams, Tom
Cc: '[EMAIL PROTECTED]'
Sent: 4/8/2004 2:42 PM
Subject: Re: Device majors incorrectly set to 0 during rsync
On Thu, Apr 08, 200
seems/ to do the right thing.
Thanks,
Tom Williams
-Original Message-
From: Wayne Davison
To: Williams, Tom
Cc: '[EMAIL PROTECTED]'
Sent: 4/8/2004 2:25 PM
Subject: Re: Device majors incorrectly set to 0 during rsync
On Thu, Apr 08, 2004 at 01:43:18PM -0700, Williams, Tom wrote:
>
On Thu, Apr 08, 2004 at 02:33:29PM -0700, Wayne Davison wrote:
> If you could retry things using the pre-release + patch, I'd
> appreciate it!
Note that my patch won't fix the problem because rsync only transmits
the lower 32 bits of the rdev value. To fix this will require a
protocol change. I'
On Thu, Apr 08, 2004 at 01:43:18PM -0700, Williams, Tom wrote:
> rsync version 2.6.0 protocol version 27
I just noticed that you aren't talking about the 2.6.1 pre-release, so
that patch I just sent won't do you any good unless you first download
that:
http://rsync.samba.org/ftp/rsync/previ
On Thu, Apr 08, 2004 at 01:43:18PM -0700, Williams, Tom wrote:
> Major numbers on 64bit Solaris are being dropped, and created as 0 on
> recieving end. 32bit version works perfectly.
Looks like the code is masking a 64-bit number with a 32-bit mask
(ouch)! Try the attached patch and let me know
OK. Didn't see anything about this in the archives, other than an old post
from 2000 about a similar problem, so here goes. Feel free to contact me if
I can provide anything else useful.
Problem:
Major numbers on 64bit Solaris are being dropped, and created as 0 on
recieving end. 32bit
