From: Carsten Aulbert <carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
To: linux-kernel@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: kernel BUG at kernel/workqueue.c:291
Date: Tue, 03 Mar 2009 08:36:21 +0100 [thread overview]
Message-ID: <49ACDDF5.8040506@aei.mpg.de> (raw)
In-Reply-To: <20090302232643.7c7ca284.akpm@linux-foundation.org>
Hi Andrew,
Andrew Morton schrieb:
>> in the mean time 43 of our nodes were struck with this error. It seems
>> that the jobs of a certain user can trigger this bug, however I have no
>> clue how to really trigger it manually.
>
> That's a lot of nodes.
Quite, at least some percentage of the whole system.
>
> Let's cc the NFS developers, see if this rpciod crash is familiar to them?
Good idea, I should have done that myself - sorry
I think we were able to pinpoint at least one user's jobs to "generate"
this, but I need to talk to him, what access patterns are used via NFS here.
Systems are running Debian Etch,
dpkg -l | awk '/(nfs|portmap)/ {print $2 "\t\t" $3}'
libnfsidmap2 0.18-0
mountnfs 1.1.3-2
nfs-common 1.0.10-6+etch.1
nfs-kernel-server 1.0.10-6+etch.1
portmap 5-26
If you need more, please let me know! So far the machines are 'on hold',
i.e. we have not yet rebooted them to be able to find out a little bit
more. If you(anyone) think we can reboot them and put back into our
scheduling queue, please let me know, the users are waiting for more cycles.
Thanks a lot
Carsten
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: linux-kernel@vger.kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: kernel BUG at kernel/workqueue.c:291
Date: Tue, 03 Mar 2009 08:36:21 +0100 [thread overview]
Message-ID: <49ACDDF5.8040506@aei.mpg.de> (raw)
In-Reply-To: <20090302232643.7c7ca284.akpm@linux-foundation.org>
Hi Andrew,
Andrew Morton schrieb:
>> in the mean time 43 of our nodes were struck with this error. It seems
>> that the jobs of a certain user can trigger this bug, however I have no
>> clue how to really trigger it manually.
>
> That's a lot of nodes.
Quite, at least some percentage of the whole system.
>
> Let's cc the NFS developers, see if this rpciod crash is familiar to them?
Good idea, I should have done that myself - sorry
I think we were able to pinpoint at least one user's jobs to "generate"
this, but I need to talk to him, what access patterns are used via NFS here.
Systems are running Debian Etch,
dpkg -l | awk '/(nfs|portmap)/ {print $2 "\t\t" $3}'
libnfsidmap2 0.18-0
mountnfs 1.1.3-2
nfs-common 1.0.10-6+etch.1
nfs-kernel-server 1.0.10-6+etch.1
portmap 5-26
If you need more, please let me know! So far the machines are 'on hold',
i.e. we have not yet rebooted them to be able to find out a little bit
more. If you(anyone) think we can reboot them and put back into our
scheduling queue, please let me know, the users are waiting for more cycles.
Thanks a lot
Carsten
next prev parent reply other threads:[~2009-03-03 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 19:48 kernel BUG at kernel/workqueue.c:291 Carsten Aulbert
2009-03-02 10:51 ` Carsten Aulbert
[not found] ` <49ABBA44.1060302-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2009-03-03 7:26 ` Andrew Morton
2009-03-03 7:26 ` Andrew Morton
2009-03-03 7:36 ` Carsten Aulbert [this message]
2009-03-03 7:36 ` Carsten Aulbert
2009-03-03 15:16 ` Trond Myklebust
2009-03-03 15:16 ` Trond Myklebust
[not found] ` <1236093413.9631.58.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-03 15:23 ` Carsten Aulbert
2009-03-03 15:23 ` Carsten Aulbert
[not found] ` <49AD4B55.5060504-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2009-03-03 20:41 ` Aaron Straus
2009-03-03 20:41 ` Aaron Straus
2009-03-03 21:21 ` Trond Myklebust
2009-03-03 21:21 ` Trond Myklebust
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=49ACDDF5.8040506@aei.mpg.de \
--to=carsten.aulbert-l1a6w7hxd2yelga04laivw@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.