Messages in this thread | | | Subject | Re: Processes spinning forever, apparently in lock_timer_base()? | From | richard kennedy <> | Date | Fri, 21 Sep 2007 11:47:33 +0100 |
| |
On Fri, 2007-09-21 at 03:33 -0700, Andrew Morton wrote: > On Fri, 21 Sep 2007 11:25:41 +0100 richard kennedy <richard@rsk.demon.co.uk> wrote: > > > > That's all a bit crappy if the wrong races happen and some other task is > > > somehow exceeding the dirty limits each time this task polls them. Seems > > > unlikely that such a condition would persist forever. > > > > > > So the question is, why do we have large amounts of dirty pages for one > > > disk which appear to be sitting there not getting written? > > > > The lockup I'm seeing intermittently occurs when I have 2+ tasks copying > > large files (1Gb+) on sda & a small read-mainly mysql db app running on > > sdb. The lockup seems to happen just after the copies finish -- there > > are lots of dirty pages but nothing left to write them until kupdate > > gets round to it. > > Then what happens? The system recovers? Nothing -- it stays stuck forever. I don't think kupdate is getting started, I added some debug in there but haven't found out anything useful yet. But I am trying to build a better test case, the one I've got at the moment can take hours to trigger this problem.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |