From: Olaf Kirch <okir@suse.de>
To: nfs@lists.sourceforge.net
Cc: Olaf Hering <olh@suse.de>
Subject: Processes stuck in D state
Date: Wed, 18 Feb 2004 17:33:05 +0100 [thread overview]
Message-ID: <20040218163305.GA31893@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi,
I spent much of today investigating a weird NFS problem on 2.6.3.
After one of our servers went away and came back, several processes on
a ppc machine were left in D state. They did not get woken up during
the whole day, until I did a "umount -f" after several hours of debugging.
The internal state of this RPC client looks a little weird. I'm
attaching some debug output that shows where they got stuck. Some
general observation:
- this does not seem a queue corruption bug, which is good :)
- the tasks were sleeping on different wait queues (pending,
sending, 1 one resend)
- all tasks have a tk_timeout value of 0
- the ntimeo values of the RTT estimators being 0 looks a
little weird, given that the mount froze because the
server wasn't reachable.
- the task on the resend queue has a timer with
tk_timer.expires != 0, but unfortunately I forgot to check whether
it was active. But I doubt it; I had debugging enabled for much
of the day and the tk_pid in question never showed up in the log
I'm not sure yet what exactly happened here. I don't understand how a
task on xprt->pending can have a timeout value of 0...
Does anyone have an idea what might be going wrong here?
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
[-- Attachment #2: nfs-messages --]
[-- Type: text/plain, Size: 1489 bytes --]
Found NFS mount, server=Hilbert2,v3,rsize=8192,wsize=8192
RPC client 6 users
Active RPC tasks for this client:
task 21384, status=-11, timeout=0, active, sleeping, on queue c45ea044(xprt_sending)
task 9969, status=-11, timeout=0, active, sleeping, on queue c45ea044(xprt_sending)
task 52431, status=-11, timeout=0, active, sleeping, on queue c45ea044(xprt_sending)
task 43528, status=-11, timeout=0, active, sleeping, on queue c45ea044(xprt_sending)
task 43527, status=-11, timeout=0, timer, async, active, sleeping, on queue c45ea050(xprt_resend)
task 55816, status=0, timeout=0, active, sleeping, on queue c45ea05c(xprt_pending)
Transport c45ea000, sockstate=0x1
cong 256/cwnd 256
RTT estimates (def timeout 700):
0: rtt 15 srtt 100 ntimeo 0
1: rtt 15 srtt 100 ntimeo 0
2: rtt 49 srtt 100 ntimeo 0
3: rtt 15 srtt 100 ntimeo 0
4: rtt 15 srtt 100 ntimeo 0
RPC wait queue sending:
task 43528, status=-11, timeout=0, active, sleeping
task 52431, status=-11, timeout=0, active, sleeping
task 9969, status=-11, timeout=0, active, sleeping
task 21384, status=-11, timeout=0, active, sleeping
RPC wait queue pending:
task 55816, status=0, timeout=0, active, sleeping
RPC wait queue resend:
task 43527, status=-11, timeout=0, active timer, async, active, sleeping
RPC wait queue backlog: empty
next reply other threads:[~2004-02-18 16:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 16:33 Olaf Kirch [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 18:32 processes stuck in D state Guolin Cheng
2003-05-06 17:09 pwitting
2003-05-06 17:31 ` Michael Buesch
2003-05-06 15:47 Lever, Charles
2003-05-06 15:18 Lever, Charles
2003-05-06 14:51 Michael Buesch
2003-05-06 15:20 ` Trond Myklebust
2003-05-06 15:41 ` Michael Buesch
2003-05-06 16:05 ` Trond Myklebust
2003-05-06 16:30 ` Michael Buesch
2003-05-06 16:54 ` Trond Myklebust
2003-05-05 5:52 Zeev Fisher
2003-05-05 14:56 ` Michael Buesch
2003-05-05 15:24 ` Mike Waychison
2003-05-05 16:25 ` Michael Buesch
2003-05-05 22:12 ` jw schultz
2001-04-04 15:47 Pau Aliagas
2001-04-07 22:07 ` Barry K. Nathan
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=20040218163305.GA31893@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=olh@suse.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.