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:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- From: Trond Myklebust <[email protected]>
- Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- References:
- pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- From: Florin Iucha <[email protected]>
- Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- From: Trond Myklebust <[email protected]>
- pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
- Next by Date: drivers/net/sunhme.c patch
- Previous by thread: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- Next by thread: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
- Index(es):
 |