Re: problem with VMware -XFS guilty one - was: Re: XFS is innocent

[Stephen Lord <lord@xxxxxxx>]

Olaf Fr1czyk wrote:

> On 2002.01.10 19:42:01 +0100 Steve Lord wrote:
>
> > On Thu, 2002-01-10 at 11:30, Olaf Fr1czyk wrote:
> > > Hi,
> > > I have installed clean RH7.2 on one free partition on my machine.
> > Removed
> > > RH gcc, installed compat-egcs, compiled new kernel (2.4.17) with xfs
> > > (using the same sources as previous) and ... no problems.
> > > So I moved kernel, modules to my working system, and ... it works.
> > > So something with my system is wrong, and the problems are not XFS
> > related.
> > > Now, I have to find what :((
>
> Hi,
>
> Found what's wrong (in my case):
> if on /tmp partition I have XFS filesystem then VMware crashes
> if on /tmp is ext2 then everything is OK
>
> The only thing VMware does on it, is to place /tmp/ram0 file (found it 
> in vmware.log).
> But it does _not_ appear in ls output, nor in mc (midnight commander).
> And I suppose, that if I have low memory, it puts them part of guest 
> OS memory.
> I think so, because the less memory I have, then I have crashes earlier.
>
> I use VMware 3.0.0 build 1455.
>
> Regards,
>
> Olaf

Please try this with the current cvs tree - there was a change in the 
last week which fixed
some problems with mmapped I/O under heavy memory pressure (the emacs 
build problem
mentioned on the list).

Steve