Hi On Mon, Jun 16, 2008 at 11:18 PM, Wendy Cheng <s.wendy.cheng@xxxxxxxxx> wrote: > howard chen wrote: > This will write all the thread backtraces into the system file > /var/log/messages file so people can have a rough idea of what goes wrong. > The *trick* here is to make sure the /var/log/messages file doesn't live on > the particular filesystem that has the high load issue (otherwise the > writing to the /var/log/messages will hang as well). So you may want to > configure the /var on a separate filesystem. Remember each ext3 filesystem > has its own kjournald (again, I have not touched ext3 for a while so this is > from my old memory). > > Another option is to google to see whether other people on the same kernel > level has the same issue as yours and pull their fix into your system - > however, it is more of a long shot (since you're doing the guessing). > > -- Wendy Thanks. I will have a more detail tests Howard ------------------------------------------------------------------------- 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
