From: "Ríkharður Egilsson" <Rikhardur.EGILSSON@oecd.org>
To: linux-kernel@vger.kernel.org
Subject: [2.2.19 reiserfs] vs-8345: get_mem_for_virtual_node: kmalloc failed.
Date: Mon, 23 Apr 2001 17:20:35 +0200 [thread overview]
Message-ID: <20010423172035.A4359@OECD.OECD.ORG> (raw)
This machine is has a 400MHz PII, Adaptec AIC-7895, 631 MB of memory,
and about 512 Meg of swap).
When compiling the kernel (2.2.19) I changed __FD_SETSIZE in
/usr/include/bits/types.h from 1024 to 8192.
(Increased number of file descriptors)
The following is executed at boot time:
# More file descriptors
echo 8192 > /proc/sys/fs/file-max
# Inodes 4x the file-max
echo 32768 > /proc/sys/fs/inode-max
# More user ports
echo 1024 32768 > /proc/sys/net/ipv4/ip_local_port_range
echo 768 > /proc/sys/net/ipv4/tcp_max_syn_backlog
echo 120 > /proc/sys/net/ipv4/tcp_fin_timeout
And I started to see this recenty :
Apr 19 11:54:24 netcache2 kernel: eth0: Memory squeeze, deferring packet.
Apr 19 11:54:24 netcache2 kernel: eth0: Memory squeeze, deferring packet.
Apr 19 11:54:33 netcache2 last message repeated 1113 times
Apr 19 11:54:33 netcache2 kernel: mem_for_virtual_node: kmalloc failed. There were 272 allocations
Apr 19 11:54:33 netcache2 last message repeated 1113 times
Apr 19 11:54:33 netcache2 kernel: mem_for_virtual_node: kmalloc failed. There were 272 allocations
Apr 19 11:54:33 netcache2 kernel: vs-8345: get_mem_for_virtual_node: kmalloc failed. There were 272 allocations
Apr 19 11:54:33 netcache2 kernel: vs-8345: get_mem_for_virtual_node: kmalloc failed. There were 272 allocations
...
...
This goes on until ...
Apr 19 11:56:45 netcache2 kernel: vs-8345: get_mem_for_virtual_node: kmalloc failed. There were 272 allocations
Apr 19 11:56:45 netcache2 last message repeated 198 times
Apr 19 11:56:53 netcache2 squid[8377]: Squid Parent: child process 8439 exited due to signal 6
Apr 19 11:56:45 netcache2 last message repeated 198 times
Apr 19 11:56:53 netcache2 squid[8377]: Squid Parent: child process 8439 exited due to signal 6
Apr 19 11:56:56 netcache2 squid[8377]: Squid Parent: child process 13195 started
Apr 19 11:56:56 netcache2 squid[8377]: Squid Parent: child process 13195 started
Is there anything I can do to prevent this from happening ?
This (squid) server, serves about 50 requests/sec, so 2 minutes of downtime
means a lot of unhappy "customers".
--
Ríkharður Egilsson - Networking/Security EXD/ITN/CCO
OECD/OCDE - Organisation for Economic Co-operation and Development
next reply other threads:[~2001-04-23 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 15:20 Ríkharður Egilsson [this message]
2001-04-23 15:33 ` Andi Kleen
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=20010423172035.A4359@OECD.OECD.ORG \
--to=rikhardur.egilsson@oecd.org \
--cc=linux-kernel@vger.kernel.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®