thr3ads.net - rsync - map_ptr warning [Feb 2002]

If this information is useful, please help other people find it:
Share via:

Bob O'Connor

2002-Feb-20 00:44 UTC

map_ptr warning

I am trying to finalize the use of rsync for updatiung a new nfs server 
before we take the old one offline.  I keep getting the following 
warning during the rsync process:

Warning: unexpected rad size of 0 in map_ptr

Any ideas where this comes from and how to make it go away?  I am using 
rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7.
Bob
roconnor@vectorpartners.com

tim.conway@philips.com

2002-Feb-20 01:37 UTC

head link

map_ptr warning

It's known.  Dave answered it Friday.
On Fri, Feb 15, 2002 at 11:08:03PM +0100, Ragnar Wisl?ff
wrote:> We're using rsync to mirror a web server. The rsync is initiated using 
> ssh from a Red Hat Linux 7.2 box, the files are located on an Alpha
> running a version of Digital Unix 4. On the Alpha rsync is 2.5.2, The
> Linux box used to have  a 2.4.6-X version, but with the map_ptr problems
> I built 2.5.2 on that as well. However, version incompatibility was not
> the problem, as they persist after the upgrade.
> 
> The problems occur in a limited number of directories, and mostly with
> graphics files. The error message is "Warning:unexpected read size of
0
> i map_ptr".
> 
> Any suggestions of what could be done to rectify this?
The problem is in 2.5.2.  Apply the patch at
    http://cvs.samba.org/cgi-bin/cvsweb/rsync/match.c.diff?r1=1.47&r2=1.48

- Dave Dykstra

Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me.... Tim?"

"Bob O'Connor" <roconnor@vectorpartners.com>
Sent by: rsync-admin@lists.samba.org
02/19/2002 06:44 AM

        To:     rsync@lists.samba.org
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        map_ptr warning
        Classification: 

I am trying to finalize the use of rsync for updatiung a new nfs server 
before we take the old one offline.  I keep getting the following 
warning during the rsync process:

Warning: unexpected rad size of 0 in map_ptr

Any ideas where this comes from and how to make it go away?  I am using 
rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7.
Bob
roconnor@vectorpartners.com

Dave Dykstra

2002-Feb-20 01:53 UTC

head link

map_ptr warning

On Tue, Feb 19, 2002 at 08:44:54AM -0500, Bob O'Connor
wrote:> I am trying to finalize the use of rsync for updatiung a new nfs server 
> before we take the old one offline.  I keep getting the following 
> warning during the rsync process:
> 
> Warning: unexpected rad size of 0 in map_ptr
> 
> Any ideas where this comes from and how to make it go away?  I am using 
> rsync 2.5.2 on Solaris 8 to pull data from rsync 2.5.2 on Solaris 7.
> Bob
> roconnor@vectorpartners.com
This is a known problem with 2.5.2.  Use 2.5.3pre1 which should become
2.5.3 real soon.

- Dave Dykstra

Charles Mount

2002-Mar-14 08:50 UTC

head link

map_ptr warning

I am using rsync-2.5.2.Solaris251.sparc from your site to synchronize from
an old  Solaris2.5.1 server in Nashville to a new Solaris8 server in
Raleigh.   I will air express tapes and use rsync to update.  I am dealing
with several hundred thousand files and a couple hundred gigabytes of data.
I use "rsync -avx --delete -e ssh old:/foo/bar/ /foo/bar >>2
/var/log/rsynclog" run as a cronjob on the new computer.
Most of the files are transferred correctly.
With a few files I get the file name followed the two copies of the line:
"Warning: unexpected read size of 0 in map_ptr"  in the log file.
In at least most cases, the next pass gives the same message on the same
file.  The file size is sometimes larger on the target and may grow on
additional passes.  If I delete the file on the target the next pass will
normally work correctly.  I see no pattern of where the problem will strike.
In some cases, the problem files are plain text with simple path and file
names.
Any ideas?

Thanks,
Charles Mount


-------------- next part --------------
HTML attachment scrubbed and removed

Jennifer Lu

2002-Mar-14 12:37 UTC

head link

map_ptr warning

Charles,

> Delivered-To: rsync@lists.samba.org
> From: "Charles Mount" <cmount@nortelnetworks.com>
> To: rsync@lists.samba.org
> Subject: map_ptr warning
> MIME-Version: 1.0
> X-BeenThere: rsync@lists.samba.org
> X-Mailman-Version: 2.0.8
> List-Help: <mailto:rsync-request@lists.samba.org?subject=help>
> List-Post: <mailto:rsync@lists.samba.org>
> List-Subscribe: <http://lists.samba.org/mailman/listinfo/rsync>, 
<mailto:rsync-request@lists.samba.org?subject=subscribe>> List-Id: rsync user list <rsync.lists.samba.org>
> List-Unsubscribe: <http://lists.samba.org/mailman/listinfo/rsync>, 
<mailto:rsync-request@lists.samba.org?subject=unsubscribe>> List-Archive: <http://lists.samba.org/pipermail/rsync/>
> Date: Wed, 13 Mar 2002 15:50:06 -0600
> 
> I am using rsync-2.5.2.Solaris251.sparc from your site to synchronize from
> an old  Solaris2.5.1 server in Nashville to a new Solaris8 server in
> Raleigh.   I will air express tapes and use rsync to update.  I am dealing
> with several hundred thousand files and a couple hundred gigabytes of data.
> I use "rsync -avx --delete -e ssh old:/foo/bar/ /foo/bar >>2
> /var/log/rsynclog" run as a cronjob on the new computer.
> Most of the files are transferred correctly.
> With a few files I get the file name followed the two copies of the line:
> "Warning: unexpected read size of 0 in map_ptr"  in the log file.
> In at least most cases, the next pass gives the same message on the same
> file.  The file size is sometimes larger on the target and may grow on
> additional passes.  If I delete the file on the target the next pass will
> normally work correctly.  I see no pattern of where the problem will
strike.
> In some cases, the problem files are plain text with simple path and file
> names.
> Any ideas?
I got the same errors. Upgrade rsync to 2.5.3 with updating batch.c file 

diff -u -r1.13 batch.c
--- batch.c     6 Feb 2002 21:20:48 -0000   1.13
+++ batch.c     12 Mar 2002 06:16:49 -0000
@@ -396,7 +396,7 @@
                   struct sum_struct *s)
 {
     size_t i;
-    unsigned int int_zero = 0;
+    size_t int_zero = 0;
     extern int csum_length;
 
     fdb_open = 1;
     
Then, re-compile it. After I compiled the new version of rsync, it works
perfectly.

     > 
> Thanks,
> Charles Mount
> 
> 
Jennifer

Jennifer Lu

2002-Mar-21 05:29 UTC

head link

map_ptr warning

Hi,

I compiled 2.5.3 rsync and used rsync between Solaris5.5.1 to Solaris5.8
without any error last week, then, we ran rsync on another two 
Solaris5.5.1 and Solaris5.8 machines, got errors:

gopher# nohup timex rsync -avSHc --delete /export/mdisk14/cafe-regres/ 
nile-ha1:/global/dg01/vmdisk009/-regres/
building file list ... ERROR: out of memory in map_ptr
rsync error: error allocating core memory buffers (code 22) at util.c(232)

real    22:07.59
user     9:58.00
sys      1:04.69


Can you please help? I just upgraded rsync from 2.5.2 to 2.5.3, do 
I need to upgrade it again? Thanks for any help.


Jennifer

Dave Dykstra

2002-Mar-22 04:53 UTC

head link

map_ptr warning

That should have been fixed in 2.5.3, are you sure you upgraded both
sides?  Unfortunately, 2.5.3 introduced a core dump in -z, which was fixed
in 2.5.4 so you should upgrade again.  More unfortunately, we just
discovered that 2.5.3 also introduced a bug which turns off the rsync
rolling checksum algorithm under some circumstances and that has not yet
been fixed in a released version.

- Dave Dykstra

On Wed, Mar 20, 2002 at 10:29:11AM -0800, Jennifer Lu
wrote:> 
> 
> Hi,
> 
> I compiled 2.5.3 rsync and used rsync between Solaris5.5.1 to Solaris5.8
> without any error last week, then, we ran rsync on another two 
> Solaris5.5.1 and Solaris5.8 machines, got errors:
> 
> gopher# nohup timex rsync -avSHc --delete /export/mdisk14/cafe-regres/ 
> nile-ha1:/global/dg01/vmdisk009/-regres/
> building file list ... ERROR: out of memory in map_ptr
> rsync error: error allocating core memory buffers (code 22) at util.c(232)
> 
> real    22:07.59
> user     9:58.00
> sys      1:04.69
> 
> 
> Can you please help? I just upgraded rsync from 2.5.2 to 2.5.3, do 
> I need to upgrade it again? Thanks for any help.
> 
> 
> Jennifer

Jennifer Lu

2002-Mar-22 04:58 UTC

head link

map_ptr warning

Hi Dave,

Thanks for the reply. Yes, both servers are running rsync2.5.3,
and you were correct, without -z and c, rsync ran successfully.
I will tell users not using -c and z between 551 and 58. 

Thanks,
Jennifer
> Date: Thu, 21 Mar 2002 11:53:57 -0600
> From: Dave Dykstra <dwd@bell-labs.com>
> To: Jennifer Lu <mou@goodluck.Eng.Sun.COM>
> Cc: rsync@lists.samba.org
> Subject: Re: map_ptr warning
> Mail-Followup-To: Dave Dykstra <dwd@bell-labs.com>, Jennifer Lu 
<mou@goodluck.Eng.Sun.COM>, rsync@lists.samba.org> Mime-Version: 1.0
> Content-Disposition: inline
> User-Agent: Mutt/1.3.27i
> 
> That should have been fixed in 2.5.3, are you sure you upgraded both
> sides?  Unfortunately, 2.5.3 introduced a core dump in -z, which was fixed
> in 2.5.4 so you should upgrade again.  More unfortunately, we just
> discovered that 2.5.3 also introduced a bug which turns off the rsync
> rolling checksum algorithm under some circumstances and that has not yet
> been fixed in a released version.
> 
> - Dave Dykstra
> 
> 
> On Wed, Mar 20, 2002 at 10:29:11AM -0800, Jennifer Lu wrote:
> > 
> > 
> > Hi,
> > 
> > I compiled 2.5.3 rsync and used rsync between Solaris5.5.1 to
Solaris5.8
> > without any error last week, then, we ran rsync on another two 
> > Solaris5.5.1 and Solaris5.8 machines, got errors:
> > 
> > gopher# nohup timex rsync -avSHc --delete /export/mdisk14/cafe-regres/
> > nile-ha1:/global/dg01/vmdisk009/-regres/
> > building file list ... ERROR: out of memory in map_ptr
> > rsync error: error allocating core memory buffers (code 22) at
util.c(232)
> > 
> > real    22:07.59
> > user     9:58.00
> > sys      1:04.69
> > 
> > 
> > Can you please help? I just upgraded rsync from 2.5.2 to 2.5.3, do 
> > I need to upgrade it again? Thanks for any help.
> > 
> > 
> > Jennifer
Jennifer

Jennifer Lu

2002-Mar-22 09:54 UTC

head link

map_ptr warning

Dave,

Yes, both machines are in the same version, here is the output:

On Solaris5.8: nile-ha1
%rsh nile-ha1 rsync --version
rsync  version 2.5.3  protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
<http://rsync.samba.org/>
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no 
IPv6,64-bit system inums, 64-bit internal inums


On Solaris 5.5.1:

64-bit system inums, 64-bit internal inums
% rsh gopher rsync --version
rsync  version 2.5.3  protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others
<http://rsync.samba.org/>
Capabilities: 32-bit files, socketpairs, hard links, symlinks, batchfiles, no 
IPv6,32-bit system inums, 64-bit internal inums

I ran "rsync -avSH --delete gopher:/export/mdisk14/cafe-regres/ 
/global/dg01/vmdisk009/cafe-regres/", it went successfully. 

Only with -avzSHc option, rsync failed with map_ptr warning. 

Thanks for the help,
Jennifer


> Date: Thu, 21 Mar 2002 12:56:47 -0600
> From: Dave Dykstra <dwd@bell-labs.com>
> To: Jennifer Lu <mou@goodluck.Eng.Sun.COM>
> Cc: rsync@lists.samba.org
> Subject: Re: map_ptr warning
> Mail-Followup-To: Dave Dykstra <dwd@bell-labs.com>, Jennifer Lu 
<mou@goodluck.Eng.Sun.COM>, rsync@lists.samba.org> Mime-Version: 1.0
> Content-Disposition: inline
> User-Agent: Mutt/1.3.27i
> 
> I'm having a hard time believing that you're seeing the map_ptr
problem in
> 2.5.3.  Nobody else has reported that, and it was specifically fixed for
> that version.  What's the output of
>     rsh nile-ha1 rsync --version
> I'm asking you to run it that way because it's possible you have
more than
> one installed, and if you rlogin you'll have a different PATH than if
> you're using rsh.
> 
> -c doesn't have anything to do with it, and neither does the operating
> system version.
> 
> By the way, -c is almost always a bad idea to put into a script because it
> has a lot of overhead.  It's mostly useful for special one-time
operations
> to get two directories in sync that hadn't previously been maintained
by
> rsync.
> 
> - Dave Dykstra
> 
> On Thu, Mar 21, 2002 at 09:58:23AM -0800, Jennifer Lu wrote:
> > 
> > Hi Dave,
> > 
> > Thanks for the reply. Yes, both servers are running rsync2.5.3,
> > and you were correct, without -z and c, rsync ran successfully.
> > I will tell users not using -c and z between 551 and 58. 
> > 
> > Thanks,
> > Jennifer
> > 
> > > Date: Thu, 21 Mar 2002 11:53:57 -0600
> > > From: Dave Dykstra <dwd@bell-labs.com>
> > > To: Jennifer Lu <mou@goodluck.Eng.Sun.COM>
> > > Cc: rsync@lists.samba.org
> > > Subject: Re: map_ptr warning
> > > Mail-Followup-To: Dave Dykstra <dwd@bell-labs.com>,
Jennifer Lu
> > <mou@goodluck.Eng.Sun.COM>, rsync@lists.samba.org
> > > Mime-Version: 1.0
> > > Content-Disposition: inline
> > > User-Agent: Mutt/1.3.27i
> > > 
> > > That should have been fixed in 2.5.3, are you sure you upgraded
both
> > > sides?  Unfortunately, 2.5.3 introduced a core dump in -z, which
was fixed
> > > in 2.5.4 so you should upgrade again.  More unfortunately, we
just
> > > discovered that 2.5.3 also introduced a bug which turns off the
rsync
> > > rolling checksum algorithm under some circumstances and that has
not yet
> > > been fixed in a released version.
> > > 
> > > - Dave Dykstra
> > > 
> > > 
> > > On Wed, Mar 20, 2002 at 10:29:11AM -0800, Jennifer Lu wrote:
> > > > 
> > > > 
> > > > Hi,
> > > > 
> > > > I compiled 2.5.3 rsync and used rsync between Solaris5.5.1
to Solaris5.8
> > > > without any error last week, then, we ran rsync on another
two
> > > > Solaris5.5.1 and Solaris5.8 machines, got errors:
> > > > 
> > > > gopher# nohup timex rsync -avSHc --delete
/export/mdisk14/cafe-regres/
> > > > nile-ha1:/global/dg01/vmdisk009/-regres/
> > > > building file list ... ERROR: out of memory in map_ptr
> > > > rsync error: error allocating core memory buffers (code 22)
at
util.c(232)> > > > 
> > > > real    22:07.59
> > > > user     9:58.00
> > > > sys      1:04.69
> > > > 
> > > > 
> > > > Can you please help? I just upgraded rsync from 2.5.2 to
2.5.3, do
> > > > I need to upgrade it again? Thanks for any help.
> > > > 
> > > > 
> > > > Jennifer
> > 
> > Jennifer
Jennifer

Reasonably Related Threads

Search for more reasonably related threads

rsync - Feb 2002 - map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

map_ptr warning

Reasonably Related Threads