From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: [9fans] odd out-of-memory behavior
Date: Fri, 25 Jul 2008 12:44:10 -0400 [thread overview]
Message-ID: <affb36fb79a62b76bfcbcbaea0a78eea@coraid.com> (raw)
i'm seeing some out-of-memory behavior i don't quite understand.
there is no swap configured. the machine is a cpuserver.
the symptom is this message is repeated on the console
maybe 20x. fs in this case is upas/fs. (the standard one.)
311954: fs killed: out of memory
out of physical memory; no swap configured
311954: fs killed: out of memory
out of physical memory; no swap configured
311954: fs killed: out of memory
there's a sleep of 5 seconds after killbig
is called. so, though it's hard to imagine,
it must be taking 100s to clean up this process.
i'm not sure i have any ideas on how this could
happen.
- erik
next reply other threads:[~2008-07-25 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:44 erik quanstrom [this message]
2008-07-25 18:09 ` Russ Cox
2008-07-25 18:25 ` erik quanstrom
2008-07-25 19:39 ` Russ Cox
2008-07-27 1:20 ` erik quanstrom
2008-07-27 2:20 ` Russ Cox
2008-07-27 2:21 ` Russ Cox
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=affb36fb79a62b76bfcbcbaea0a78eea@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).