On Wed, 1 Jul 1998 jaharkes_at_cs.cmu.edu wrote:

> > Rdsinit will initialize data and log.
> > This takes a while.
> > rvm_initialize succeeded.
> > Going to initialize data file to zero, could take awhile.
> > done.
> > ?  ERROR: rds_zap_heap RVM_EINTERNAL.
> > Error in rdsinit. Exiting.
> 
> RVM_EINTERNAL is returned when the allocation of virtual memory fails. This is 
> used to store the in memory copy of the rvm. The result is that your rvm data 
> file can not be initialized correctly.
> 
> Why it fails, I'm not sure. I'll give a list of questions at the end of this 
> mail.
> 
> > Error rvm_load_segment returns 201
> > 00:19:15 rds_load_heap error RVM_EINTERNAL
> > 
> > This appears in the SrvErr log:
> > 
> > Assertion failed: file
> > "/usr/src/redhat/BUILD/coda-4.6.0/coda-src/vice/srv.cc", line 1805
> 
> As the rvm is not initialized, it cannot be loaded correctly, (or more likely 
> as 201 == RVM_EINTERNAL the mmap fails again.
> 

Hi Jan!


> - What is the rvm data file size you tried to create.

I took one of the choices offered by vice-setup; 90M.


> - How much physical memory does your system have.

The libc-5.4.44 box has 64M of physical memory.
The glibc box has 32M of physical memory.

> - How much swap memory.

The libc5 box has 20M of swap.
The glibc box has 60M of swap.

> - Is the rvm data stored in a file or on a separate partition.

A separate partition in both cases.  This is also true for the log.

> - What is the architecture of your machine (x86 or sparc?).

The libc5 machine is a Cyrix 6x86 P150+, and the glibc machine is a Cyrix
200MMX.

I'll be glad to try anything reasonable in an effort to mitigate this.

Steve