map_ptr warning
Dave Dykstra
dwd at bell-labs.com
Fri Mar 22 05:56:47 EST 2002
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 at bell-labs.com>
> > To: Jennifer Lu <mou at goodluck.Eng.Sun.COM>
> > Cc: rsync at lists.samba.org
> > Subject: Re: map_ptr warning
> > Mail-Followup-To: Dave Dykstra <dwd at bell-labs.com>, Jennifer Lu
> <mou at goodluck.Eng.Sun.COM>, rsync at 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
More information about the rsync
mailing list