On Fri, 21 Sep 2007 11:25:41 +0100 richard kennedy <[email protected]> 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?
-
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/
- References:
- Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
- Re: Processes spinning forever, apparently in lock_timer_base()?
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]