On Mon, 2007-10-29 at 10:01 -0500, Florin Iucha wrote: > 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
I can't see any evidence of NFS traffic at all in those traces, but there is a fuse process that is sleeping in :fuse:fuse_dev_read(). Could that perhaps be relevant. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
