From: "Sergey S. Kostyliov" <rathamahata@php4.ru>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
"Alexander Y. Fomichev" <gluk@php4.ru>,
anton@megashop.ru
Subject: Re: 2.6.1 IO lockup on SMP systems
Date: Tue, 24 Feb 2004 14:56:20 +0300 [thread overview]
Message-ID: <200402241456.20856.rathamahata@php4.ru> (raw)
In-Reply-To: <403A70EB.4060909@matchmail.com>
On Tuesday 24 February 2004 00:30, Mike Fedyk wrote:
> Sergey S. Kostyliov wrote:
> > Hello Andrew,
> >
> > Now this happens for the third time.
> >
> >
> >>>>I've just reproduced this lockup with 2.6.3.
> >>>>
> >>>>
> >>>>>You may need a serial console to be able to capture all the output.
> >>>>>
> >>>>>Also, it would be useful to know what sort of load the machines are
> >>>>>under, and what filesystems are in use.
> >>>>
> >>>>The machine is a http server. The main applications are:
> >>>>1) apache 1.3 which serves php pages (mod_php):
> >>>> 15.3 requests/sec - 111.9 kB/second - 7.3 kB/request
> >>>> 54 requests currently being processed, 19 idle servers
> >>>>2) mysql:
> >>>> Threads: 19 Questions: 26922012 Slow queries: 9799 Opens: 64980
> >>>> Flush tables: 1 Open tables: 630 Queries per second avg: 143.547
> >>>>
> >>>>This is an IO bound machine in general. All filesystems are reiserfs.
> >>>>
> >>>>Here is a sysrq-T output obtained from a locked box via serail console:
> >>>
> >>>OK, so everything is stuck trying to allocate memory. Perhaps you ran out
> >>>of swapspace, or some process has gone berzerk allocating memory.
> >
> >
> > The memory exhaustion is indeed possible for this box. I'll double check
> > ulimit and /etc/security/limits.conf stuff. The only thing which worries
> > me that this box had been running for months without any problems with
> > 2.4.23aa1.
> >
> > I have added another 2Gb to swap space (hope this give enough time
> > to find the memory hungry process(es)).
>
> Also check how much memory is being used for slab in /proc/meminfo
Thanks for the hint, will do this next time.
--
Best regards,
Sergey S. Kostyliov <rathamahata@php4.ru>
Public PGP key: http://sysadminday.org.ru/rathamahata.asc
next prev parent reply other threads:[~2004-02-24 11:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 16:40 2.6.1 IO lockup on SMP systems Sergey S. Kostyliov
2004-02-01 0:17 ` Andrew Morton
2004-02-21 16:45 ` Sergey S. Kostyliov
2004-02-21 19:30 ` Andrew Morton
2004-02-22 17:39 ` Alexander Y. Fomichev
2004-02-23 17:27 ` Sergey S. Kostyliov
2004-02-23 21:30 ` Mike Fedyk
2004-02-24 11:56 ` Sergey S. Kostyliov [this message]
2004-02-23 22:26 ` Andrew Morton
2004-02-24 7:23 ` Marcelo Tosatti
2004-02-24 6:53 ` Andrew Morton
2004-02-24 11:54 ` Sergey S. Kostyliov
2004-02-26 12:19 ` Sergey S. Kostyliov
2004-02-26 12:53 ` Andrew Morton
2004-02-26 13:11 ` Andrew Morton
2004-02-26 14:37 ` Dave Jones
2004-02-26 15:37 ` Arjan van de Ven
2004-02-26 14:30 ` Sergey S. Kostyliov
2004-02-26 20:03 ` Andrew Morton
2004-02-28 14:56 ` Sergey S. Kostyliov
2004-04-08 9:08 ` 2.6.X kernel memory leak? (was: Re: 2.6.1 IO lockup on SMP systems) Sergey S. Kostyliov
2004-04-09 7:17 ` 2.6.X kernel memory leak? Sergey S. Kostyliov
2004-04-09 9:09 ` Andrew Morton
2004-04-09 12:15 ` Sergey S. Kostyliov
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=200402241456.20856.rathamahata@php4.ru \
--to=rathamahata@php4.ru \
--cc=akpm@osdl.org \
--cc=anton@megashop.ru \
--cc=gluk@php4.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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