Christian Robottom Reis wrote: > On Fri, May 09, 2008 at 11:43:05AM -0400, J. Bruce Fields wrote: > > >> Perhaps a sysrq-T dump of lockd would show where (and whether) it's >> blocked? (So once lockd stops responding, log into the server, run >> "echo t >/proc/sysrq-trigger", and collect the output from the logs, >> especially the stacktrace for the lockd process). >> Sorry, I was debugging some other stuffs on my screen while mindlessly reading the mailing list - somehow missed Bruce's original "sysrq-t" paragraph. However, look like you've missed the "w" part. My guess is that the lockd was spinning on the CPU when you hit the sysrq-t key or your sysrq-t didn't run to its completion at all. -- Wendy ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
