From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Ramy M. Hassan" <ramy@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kswapd problem
Date: Mon, 21 Jun 2004 16:56:50 -0300 [thread overview]
Message-ID: <20040621195650.GA13944@logos.cnet> (raw)
In-Reply-To: <20040612153247.13279.qmail@gawab.com>
On Sat, Jun 12, 2004 at 03:32:47PM +0000, Ramy M. Hassan wrote:
>
> kswapd and kupdated are causing our production server to
> completely freezeup for few seconds every now and then.
> The server is running kernel 2.4.26SMP on a Dual Xeon 2.20GHz
> with 4GB RAM, 900GB FC RAID Qlogic HBA using driver qla2300.o
> and reiserfs.
> The RAID filesystem contains millions of files in thousands of
> directories.
> The system is under fair load. Normally the load avarage is
> about 3 and everything works properly, but suddenly the system
> stops responding except to ping, and stay freezed for about 20
> seconds, during that time I can not even type anything, then the
> system becomes responsive again and I see the load avarge over
> 250 and starts to decrease till it is back to 3 , then few
> minutes later that same thing is repeated.
> I noticed that at the time of the freezups both kswapd and
> kupdated are the most active processes each consuming over 30%
> of the CPU ( kswapd is usually more than kupdated )
Hi Ramy,
Can you get us some more data when this happens?
What are the size's of the page lists (/proc/meminfo) when the freeze happens,
can you capture that?
Also leave vmstat running in the background.
If you are willing to debug I'm sure we will be able to find the
reason for the problem.
next prev parent reply other threads:[~2004-06-21 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 15:32 kswapd problem Ramy M. Hassan
2004-06-21 19:56 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-25 13:26 Ulrich Brand
2004-07-09 14:20 Ulrich Brand
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=20040621195650.GA13944@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ramy@gawab.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