From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: akpm@zip.com.au
Subject: Re: Insanely high "Cached" value
Date: Fri, 16 Nov 2001 10:54:21 +0100 [thread overview]
Message-ID: <3BF4E24D.2E7567A7@TeraPort.de> (raw)
> Re: Insanely high "Cached" value
>
> From: Andrew Morton (akpm@zip.com.au)
> Date: Sat Nov 10 2001 - 00:17:01 EST
>
>
> Steven Walter wrote:
> >
> > My system has been running a little over twelve days now, and I just
> > noticed that the "Cached" value in both 'free' and /proc/meminfo is
> > insanely high. This wasn't the case the last time I checked, which was
> > probably a day ago.
> >
> > Just before checking it this time, I ran a "du -s *" in /usr, which
> > generated a lot of I/O, as it to be expected. Perhaps the large amount
> > of I/O has uncovered a bug of some sort?
> >
> > This is kernel 2.4.13 (hopefully it's not something that's already been
> > reported and fixed; I haven't seen it if is has) patched with ext3, kdb,
> > lm_sensors, and the pre-empt patch. Seems likely to be only a simple VM
> > problem, however, and an asthetic one at that.
>
> It's an ext3 bug. Harmless, fixed in the (ext3-enriched) 2.4.15-pre2.
>
Hmm. Are you sure it is ext3 only? I see the same (coming and going, no
real harm) on 2.4.13-ac4+preempt without having EXT3 enabled. Also
happens with 2.4.13 plain.
# CONFIG_EXT3_FS is not set
CONFIG_EXT2_FS=y
Martin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
next reply other threads:[~2001-11-16 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 9:54 Martin Knoblauch [this message]
2001-11-16 15:50 ` Insanely high "Cached" value Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-11-10 5:04 Steven Walter
2001-11-10 5:17 ` Andrew Morton
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=3BF4E24D.2E7567A7@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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