From: Jim Eshleman <jce0@Lehigh.EDU>
To: Jim Eshleman <jce0@Lehigh.EDU>
Cc: Jason Allen <jallen@fnal.gov>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: 2.4.13 Mem Related Hangs
Date: Tue, 13 Nov 2001 10:54:59 -0500 [thread overview]
Message-ID: <3BF14253.1060008@Lehigh.EDU> (raw)
In-Reply-To: <3BE6C909.6070308@Lehigh.EDU>
> FWIW me too, on an 8-way 8.5GB (64GB HIGHMEM enabled) IBM Netfinity
> x370 (8500R) which functions as a production mail server. I currently
> run 2.4.9 with XFS and it stays up for about a week under heavy load.
> 2.4.13 lasted about 4 hours under light load until all memory was
> consumed by cache then it became unresponsive.
>
> 2.4.13 on a 2-way 1GB (64GB HIGHMEM enabled) Netfinity x350 test box
> with the same kernel config and XFS works fine even under stress, so
> perhaps our problem is similar to the discussion on l-k "Google's mm
> problems"...
Update: I'm unable to make 2.4.14 fail on the test box (running
Cerberus, bonnie++ against two XFS volumes, and LTP simultaneously) but
it melts-down just as 2.4.13 does on the big production box. A short
time after all memory is eaten by file cache, and under light load, the
machine becomes unresponsive. It took about five minutes to login at
the console. No error messages on the console or in syslog. Here's
some info, it's obvious in the vmstat output where the melt-down occurs:
kernel config: http://www.lehigh.edu/~jce0/2.4.14-config
bootup messages: http://www.lehigh.edu/~jce0/2.4.14-messages
vmstat 60 output: http://www.lehigh.edu/~jce0/2.4.14-vmstat
ver_linux output: http://www.lehigh.edu/~jce0/ver_linux.out
This is linus 2.4.14 patched with linux-2.4.14-xfs-2001-11-06.patch
and LVM 0.9.1_beta6, compiled with egcs-2.91.66. It's a RH 7.1 system.
I know Andrea and Marcelo? were testing and fixing some HIGHMEM
things. Were there any patches and did they make it into the Linus tree?
Any assistance greatly appreciated.
Jim
next prev parent reply other threads:[~2001-11-13 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 17:14 2.4.13 Mem Related Hangs Jim Eshleman
2001-11-13 15:54 ` Jim Eshleman [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-05 15:29 Jason Allen
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=3BF14253.1060008@Lehigh.EDU \
--to=jce0@lehigh.edu \
--cc=jallen@fnal.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).