From: Florin Iucha <florin@iucha.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
Date: Mon, 29 Oct 2007 10:01:55 -0500 [thread overview]
Message-ID: <20071029150154.GC25561@iucha.net> (raw)
In-Reply-To: <1193665619.7396.8.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Mon, Oct 29, 2007 at 09:46:59AM -0400, Trond Myklebust wrote:
> > What could cause this? I use NFS4 to automount the home directories
> > from a Solaris10 server, and this box found a few bugs in the NFS4
> > code (fixed in the 2.6.22 kernel).
> >
> > I'll try running with 2.6.23 again for a few days, to see if I get the
> > pdflush stuck. Any other ideas?
>
> One of them appears to be waiting for i/o congestion to clear up. If the
> filesystem is NFS, then that means that some other thread is busy
> writing data out to the server. You'll need to look at the rest of the
> thread dump to figure out which thread is writing the data out, and
> where it is getting stuck.
Trond,
The full dmesg is at http://iucha.net/2.6.24-rc1/dmesg.stuck_pdflush.gz
Cheers,
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-29 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 15:24 pdflush stuck in D state with v2.6.24-rc1-192-gef49c32 Florin Iucha
2007-10-29 13:46 ` Trond Myklebust
2007-10-29 15:01 ` Florin Iucha [this message]
2007-10-29 18:43 ` Trond Myklebust
2007-10-29 18:48 ` Florin Iucha
[not found] ` <E1ImlvH-0003YH-Qf@localhost>
2007-10-30 7:54 ` Fengguang Wu
2007-10-30 11:42 ` Florin Iucha
[not found] ` <E1ImpbK-0000l3-1u@localhost>
2007-10-30 11:49 ` Fengguang Wu
2007-10-30 11:55 ` Florin Iucha
2007-10-31 0:02 ` Florin Iucha
2007-10-31 3:52 ` Florin Iucha
[not found] ` <E1In7S9-0001rv-NO@localhost>
2007-10-31 6:53 ` Fengguang Wu
2007-10-31 12:16 ` Florin Iucha
2007-10-31 17:53 ` Florin Iucha
[not found] ` <E1InUH6-0001vE-1Y@localhost>
2007-11-01 7:15 ` Fengguang Wu
2007-11-01 12:25 ` Florin Iucha
[not found] ` <E1InZht-0004lr-NN@localhost>
2007-11-01 13:03 ` Fengguang Wu
2007-11-01 14:14 ` Florin Iucha
[not found] ` <E1InlPV-0001f1-SL@localhost>
2007-11-02 1:33 ` Fengguang Wu
2007-11-02 2:10 ` Florin Iucha
[not found] ` <E1Inw51-0001e8-PS@localhost>
2007-11-02 12:56 ` Fengguang Wu
2007-11-02 13:32 ` Florin Iucha
2007-11-11 13:43 ` Thomas
2007-12-04 10:28 ` [Bug 9291] " Ingo Molnar
2007-12-04 17:45 ` Thomas Kuther
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=20071029150154.GC25561@iucha.net \
--to=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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