From: Steven Walter <srwalter@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: andrea@e-mind.com
Subject: Insanely high "Cached" value
Date: Fri, 9 Nov 2001 23:04:39 -0600 [thread overview]
Message-ID: <20011109230439.A13013@hapablap.dyn.dhs.org> (raw)
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.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
Freedom is slavery. Ignorance is strength. War is peace.
-- George Orwell
Those that would give up a necessary freedom for temporary safety
deserver neither freedom nor safety.
-- Ben Franklin
He's alive. He's alive! Oh, that fellow at RadioShack said I was mad!
Well, who's mad now?
-- Montgomery C. Burns
next reply other threads:[~2001-11-10 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 5:04 Steven Walter [this message]
2001-11-10 5:17 ` Insanely high "Cached" value Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2001-11-16 9:54 Martin Knoblauch
2001-11-16 15:50 ` Robert Love
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=20011109230439.A13013@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=andrea@e-mind.com \
--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