From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Jens Axboe <axboe@suse.de>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: kblockd/1: page allocation failure in 2.6.9
Date: Mon, 10 Jan 2005 10:19:39 +0100 [thread overview]
Message-ID: <41E248AB.5020004@bio.ifi.lmu.de> (raw)
In-Reply-To: <41CF3BBC.9010304@bio.ifi.lmu.de>
Hi,
we can now reproduce the problem, but it looks like the problems are
not caused by the kblockd.
The problem on this host is that from time to time "ps -aux" just hangs
and starts eating up all memory. When it has taken enough, either some
kblockd message occurs, and/or the oom killer jumps in and starts killing
threads.
So, the ps -aux hangs *before* the kblockd messages occur, and is not
caused by it (like I assumed before). And since I don't get any disk
errors etc. after the kblockd messages, I guess everything is fine and
the scsi operation indeed recovers the way you said it should.
Now we just need to find out why ps -aux hangs. Seems to be a problem
with the nfsd, because it hangs when showing the [nfsd] entries and
works after restarting the nfs server. In case someone is interested
in this issue, I described it in more detail on the nfs list at
http://marc.theaimsgroup.com/?l=linux-nfs&m=110509676609987&w=2
Thanks for your help!
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
prev parent reply other threads:[~2005-01-10 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 7:39 kblockd/1: page allocation failure in 2.6.9 Frank Steiner
2004-12-23 11:26 ` Frank Steiner
2004-12-23 15:51 ` Denis Vlasenko
2004-12-23 15:55 ` Frank Steiner
2004-12-24 13:20 ` Jens Axboe
2004-12-24 19:28 ` James Bottomley
2004-12-25 22:49 ` Frank Steiner
2004-12-26 15:46 ` James Bottomley
2004-12-26 22:31 ` Frank Steiner
2005-01-10 9:19 ` Frank Steiner [this message]
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=41E248AB.5020004@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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