> > After this, I stopped seeing errors in dmesg. Great! However there is > > still a deadlock in the filesystem. For example, an Apache process can > > block for several minutes trying to read a file. During this time the > > process is unkillable, load goes well over 100, aufs cannot be > > remounted, and everything becomes unresponsive. This happened twice > > today. > > I am not sure the patch for vmscan is related to the problem. > If you can, try MagicSysRq + D, T, W, if you enable it. > It will show which process and where in it stopped.
One more thing to confirm. What is your ubuntu kernel version? Hardy 2.6.24-24 kernel has several variants. For instance here are the tag names in ubuntu-hardy GIT tree. Ubuntu-2.6.24-24.50 Ubuntu-2.6.24-24.51 Ubuntu-2.6.24-24.53 Ubuntu-2.6.24-24.54 Ubuntu-2.6.24-24.55 Ubuntu-2.6.24-24.56 Ubuntu-2.6.24-24.57 Anyway I believe that your kernel has to be Ubuntu-2.6.24-24.XX. So I want you to build and test your hardy kernel without the patch for vmscan first. With this test, we will be able to make sure whether the cause of deadlock is in the patch or not, I hope. J. R. Okajima ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
