From: Octave <oles@ovh.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: 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:03:12 +0100 [thread overview]
Message-ID: <20031221150312.GJ25043@ovh.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0312211235010.6632@logos.cnet>
On Sun, Dec 21, 2003 at 12:37:44PM -0200, Marcelo Tosatti wrote:
>
>
> On Sun, 21 Dec 2003, Peter Zaitsev wrote:
>
> > On Sun, 2003-12-21 at 03:14, Octave wrote:
> > > Hi,
> > > Since we use 2.4.23 we have lot of crash. I have no kernel panic.
> > > All I can report is this kind of syslog's message:
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process rateup
>
> How much swap do you have in your system?
>
> This is happening because the system is unable to free memory (you
> probably ran out of swap for some reason).
Marcelo,
For exemple this server: Piv 2.4GHz with 1Go RAM
I think it arrives when all memory is used (ram + swap).
# free
total used free shared buffers cached
Mem: 1032592 1016492 16100 0 36184 759668
-/+ buffers/cache: 220640 811952
Swap: 265064 122784 142280
# ps auxw | grep -v "0 0.0"
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
mysql 26958 0.0 14.0 275000 144972 ? S Dec19 2:09 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
mysql 27004 0.0 14.0 275000 144972 ? S Dec19 2:28 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
mysql 27005 0.0 14.0 275000 144972 ? S Dec19 2:03 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
root 9621 0.0 0.1 6316 1860 ? S 01:02 0:00 /usr/sbin/sshd
root 9631 0.0 0.1 2500 1352 pts/0 S 01:02 0:00 -bash
root 9683 0.0 0.1 6276 1844 ? S 13:47 0:00 /usr/sbin/sshd
root 9707 0.0 0.1 2504 1356 pts/2 S 13:47 0:00 -bash
postfix 29728 0.0 0.1 3508 1184 ? S 15:45 0:00 pickup -l -t fifo -u
mysql 7341 0.0 14.0 275000 144972 ? S 15:59 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --
root 7347 0.0 0.1 2504 1356 pts/2 R 15:59 0:00 -bash
There is nothing to take 1Go of RAM.
I switched to 2.4.22 some servers and there is no more problem with. So I think
it's 2.4.23's problem only.
Octave
next prev parent reply other threads:[~2003-12-21 15:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 0:14 lot of VM problem with 2.4.23 Octave
2003-12-21 9:30 ` Peter Zaitsev
2003-12-21 14:37 ` Marcelo Tosatti
2003-12-21 15:03 ` Octave [this message]
2003-12-21 15:42 ` Willy Tarreau
2003-12-21 16:13 ` Octave
2003-12-21 18:45 ` Marcelo Tosatti
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=20031221150312.GJ25043@ovh.net \
--to=oles@ovh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=peter@mysql.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