From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Octave <oles@ovh.net>
Cc: Willy Tarreau <willy@w.ods.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Peter Zaitsev <peter@mysql.com>,
linux-kernel@vger.kernel.org
Subject: Re: lot of VM problem with 2.4.23
Date: Sun, 21 Dec 2003 16:45:38 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.58L.0312211643470.6632@logos.cnet> (raw)
In-Reply-To: <20031221161324.GN25043@ovh.net>
On Sun, 21 Dec 2003, Octave wrote:
> > one of my collegues had a server which occasionally crashed at night with
> > mysql taking all the memory. I think it was with an old 2.4.18 kernel. He
> > finally reinstalled all the machine and it never happened anymore. So
> > eventhough it works for you with 2.4.22, perhaps 2.4.23 triggers a mysql
> > bug which is fixed in more recent releases ?
>
> Willy,
> Hmm ... could be, but I don't think so. I use last mysql3 version and
> I have this problem without mysql too.
>
> For example on this box there is no mysql (Piv 2.4GHz/512Mo):
> __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> VM: killing process watchdog
> __alloc_pages: 1-order allocation failed (gfp=0x1f0/0)
> __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> VM: killing process watchdog
>
> # free
> total used free shared buffers cached
> Mem: 514468 508416 6052 0 11608 205464
> -/+ buffers/cache: 291344 223124
> Swap: 265032 77524 187508
>
> When I swithed more that 700 servers 10-15 days ago to 2.4.23, I saw that
> servers swaped less that with 2.4.22. So I believe VM was modified. Cool.
> Great job. Now servers begin to crash :/
Octave,
Can you please "echo 1 > /proc/sys/vm_gfp_debug" (to turn VM debugging on)
and rerun the tests which crash the box.
Also run "vmstat 5" in the background and save that to a file.
next prev parent reply other threads:[~2003-12-21 18:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 0:14 Octave
2003-12-21 9:30 ` Peter Zaitsev
2003-12-21 14:37 ` Marcelo Tosatti
2003-12-21 15:03 ` Octave
2003-12-21 15:42 ` Willy Tarreau
2003-12-21 16:13 ` Octave
2003-12-21 18:45 ` Marcelo Tosatti [this message]
2003-12-21 19:14 ` Octave
2003-12-21 20:45 ` Marcelo Tosatti
2003-12-21 21:09 ` Octave
2003-12-21 22:23 ` Willy Tarreau
2003-12-22 7:03 ` Ville Herva
2003-12-22 18:35 ` Mike Fedyk
2003-12-22 21:12 ` Ville Herva
2003-12-22 22:52 ` Gene Heskett
2003-12-23 8:51 ` Ville Herva
2003-12-22 19:09 ` Andrea Arcangeli
2003-12-22 21:18 ` Ville Herva
2003-12-21 18:47 ` Octave
2003-12-21 18:59 ` Tomas Szepe
2003-12-21 23:43 ` Octave
2003-12-22 11:27 ` Marcelo Tosatti
2003-12-22 12:30 ` Octave
2003-12-22 15:17 ` Andrea Arcangeli
2003-12-23 22:59 ` Octave
2003-12-21 10:43 ` bert hubert
[not found] <14ZDV-1H1-1@gated-at.bofh.it>
2003-12-21 13:53 ` Kristian
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=Pine.LNX.4.58L.0312211643470.6632@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oles@ovh.net \
--cc=peter@mysql.com \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®