All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: stuck nfsd processes with 2.6.24-rc2
Date: Tue, 13 Nov 2007 14:41:13 -0500	[thread overview]
Message-ID: <20071113194113.GA22590@fieldses.org> (raw)
In-Reply-To: <alpine.DEB.0.9999.0711131955530.27452@sheep.housecafe.de>

On Tue, Nov 13, 2007 at 08:07:55PM +0100, Christian Kujau wrote:
> I noticed that I cannot use kernel nfsd any more with 2.6.24-rc2, last 
> working kernel as of now is 2.6.23.1. First I was using nfsv4 but switching 
> to nfsv3 did not help either: exported shares can be mounted (client: 
> 2.6-git/powerpc32, nfs-common-1.1.1~git-20070709-3ubuntu1), but running "ls 
> /mountpoint" (even without "-l") on the client is enough to get the [nfsd] 
> processes in "D" state.
> Restarting the rpc.nfsd process on the does not help much, the new rpc.nfsd 
> processes get stuck quickly.
>
> For more details please see http://nerdbynature.de/bits/2.6.24-rc2/nfsd/
>
> I haven't seen this particular issue on the list recently, hence my post.
> I'll try to git-bisect my way through the changesets, but it'll take some 
> time...

Could you get a sysrq-T trace?  (First get the [nfsd] processes in [D]
state.  Then type sysrq-T, or "echo t >/proc/sysrq-trigger".  Then
extract the stuff that's dumped to the logs.)

--b.

  reply	other threads:[~2007-11-13 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 19:07 stuck nfsd processes with 2.6.24-rc2 Christian Kujau
2007-11-13 19:41 ` J. Bruce Fields [this message]
2007-11-13 21:27   ` Christian Kujau
2007-11-14  1:36     ` Christian Kujau
2007-11-14  3:23       ` J. Bruce Fields
2007-11-13 20:45 ` Mathieu Desnoyers

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=20071113194113.GA22590@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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.