linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-mm@kvack.org, Con Kolivas <contest@kolivas.net>
Subject: Re: VM trouble, both 2.4 and 2.5
Date: Sat, 16 Nov 2002 01:18:40 +0100	[thread overview]
Message-ID: <02111601184000.00209@7ixe4> (raw)
In-Reply-To: <3DD578D1.1E3134A0@digeo.com>

On Friday 15 November 2002 23:44, Andrew Morton wrote:

> Are you *sure* it happens with ext2?  Checked /proc/mounts to ensure
> that /tmp is really ext2?

Darn it!

You are absolutely correct, /tmp was on /, ext3 builtin, ext2 as module, so 
it was really still ext3. /bin/mount lied to me. When I moved /tmp to its own 
partition, really ext2 this time, things stopped misbehaving. That ext2/ext3 
thing was the very first thing I tried, wasted a lot of time :-(

> I could certainly believe that the (weird) ext3 behaviour would upset
> the overcommit beancounting though.  Hundreds of megabytes of memory
> on the inactive list but not in pagecache probably looks like anonymous
> memory to the overcommit logic.

Does this bit mean the report was still somewhat useful (for fixing either 
ext3 or the overcommit accounting) though, or was it already well-known?

Well, anyways, thanks heaps for the explanation, was going slowly mad here ...

Rene.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-11-16  0:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 22:21 Rene Herman
2002-11-15 22:44 ` Andrew Morton
2002-11-16  0:18   ` Rene Herman [this message]
2002-11-16  0:39     ` Andrew Morton
2002-11-16  0:59       ` Rene Herman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02111601184000.00209@7ixe4 \
    --to=rene.herman@keyaccess.nl \
    --cc=akpm@digeo.com \
    --cc=contest@kolivas.net \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox