On Mon, 2 Aug 1999, Peter J. Braam wrote:

> The first think I'd do is to have a close look at /proc/"pid"/mmap and find
> out if the address space used by shared libraries is colliding with with
> what you are mapping in using RVM.
> 
> RVM is mapped at 0x20000000 and you need a good 500M above that to be free.

One of our guys just checked that and he says the memory region looks fine
(see attachment).  I should add that I tried it with some of the standard
scripted configurations (using vice-setup-rvm) with the following results:

	LOG SIZE		DATA SIZE		SUCCESS
	--------		---------		-------
	22			12			yes
	22			30			yes
	90			12			yes
	200			30			yes
	315			30			no

BTW we're running a Linux 2.2.9 kernel with the standard RedHat 6.0
glibc2.1 and libs (i.e. we had RedHat 5.0 and then I upgraded all the
RPM's to 6.0 manually).  If I get some time I'll try to dig through the
rdsinit source codes and find out what line is generating the error.  :-/

-Pete

-------Forwarded Message-------
>From bguppy_at_tasc.com Mon Aug  2 13:55:36 1999
Date: Mon, 2 Aug 1999 13:41:26 -0400 
From: "Guppy, Brian" <bguppy_at_tasc.com>
To: 'Pete Gonzalez' <gonz_at_ratloop.com>
Subject: RE: Error running rdsinit (fwd)


> The first think I'd do is to have a close look at /proc/"pid"/mmap and find
> out if the address space used by shared libraries is colliding with with
> what you are mapping in using RVM.
> 
> RVM is mapped at 0x20000000 and you need a good 500M above that to be free.

I just looked at the maps, and shared library mapping starts at
0x40000000, which should give us 2*16^7, or 512MB of space for RVM, which
fails to explain why the 315MB choice (and your initial attempt with
500MB) didn't work.  Unless, for some reason, RVM mapping is
non-contiguous, which doesn't seem likely.  Have you experimented any more
to see what is the largest size you can specify without getting the error
message?

-Brian