Bug 10837 - rpciod stuck in 'D' state
Summary: rpciod stuck in 'D' state
Status: CLOSED CODE_FIX
Alias: None
Product: File System
Classification: Unclassified
Component: NFS (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Trond Myklebust
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-30 01:40 UTC by Rafal Wijata
Modified: 2010-01-19 17:52 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.24.4-64.fc8
Subsystem:
Regression: No
Bisected commit-id:

Attachments
echo w > sysrq-trigger # output (5.40 KB, text/plain)
2008-05-30 01:43 UTC, Rafal Wijata 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Rafal Wijata 2008-05-30 01:40:03 UTC 
Latest working kernel version:
Earliest failing kernel version:
Distribution: Fedora 8
Hardware Environment:
Software Environment:
Problem Description:

I have nfs mounts mounted via automount. Suddenly it stopped working.
After short investigation, appeared that kernel helper thread stuck in 'D' state - refer attachement for "echo w > /proc/sysrq-trigger" output

Steps to reproduce:
Comment 1 Rafal Wijata 2008-05-30 01:43:12 UTC 
Created attachment 16334 [details]
echo w > sysrq-trigger # output
Comment 2 Trond Myklebust 2008-05-30 11:24:12 UTC 
This should already be fixed in 2.6.25, where rpciod is no longer
responsible for closing the open context, and therefore cannot get into
a situation where it calls rpc_shutdown_client on itself.
Note You need to log in before you can comment on or make changes to this bug.