Insanely high "Cached" value
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.
Signature · 11 lines
-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
Quoted 6 lines · Steven Walter
My system has been running a little over twelve days now, and I just noticed that the "Cached" value in both 'free' and
/proc/meminfois insanely high. This wasn't the case the last time I checked, which was probably a day ago.
Quoted 8 lines
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.
-