CAM disk I/O starvation

[Adrian Chadd]

On 17 April 2012 12:15, Gary Jennejohn <gljennjohn at googlemail.com> wrote:

> Yes, I agree completely.  My first thought was that disk I/O
> scheduling had somehow been pessimized.  But then I thought -
> wait a minute, I have disk caches enabled and command queuing is
> enabled for all of them, so that shouldn't really have any
> noticeable impact.  So I was at a loss to explain why disk performance
> had suddenly gotten so bad.

That's assuming there are no bugs anywhere. :)

> I'd be willing to spend some time on diagnosing it, but I have to come
> up with a scenario which would reliably reproduce the problem.  AFAICR
> it generally happened when I was running csup/svn because my CVS
> repositoy is on one disk and /usr/{ports,src} are on a different one.
>
> I still have the old problem kernel around, but it's probably not
> instrumented for any meaningful diagnoses.

Well do you know which version of which tree you used to build that?
If it's head, you could "just" keep an earlier source tree around to
build a kernel from.



Adrian