<div class="gmail_quote">On Wed, Mar 24, 2010 at 6:36 PM, Daniel Pittman <span dir="ltr"><<a href="mailto:daniel@rimspace.net">daniel@rimspace.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">David Harrison <<a href="mailto:david.harrison@stress-free.co.nz">david.harrison@stress-free.co.nz</a>> writes:<br>
<br>
</div><div class="im">> I will try the deadline scheduler tonight and see if that makes a<br>
> difference.<br>
<br>
</div>You should be able to make the change at run-time, through sysfs, I believe.<br>
It is a property of the hardware devices, IIRC, in sysfs.<br></blockquote><div><br></div><div><br></div><div>I tried out a few of the schedulers and none of them helped the problem.</div><div>If anything I'd have to say it got worse.</div>
<div><br></div><div>As a final test I have switched to the kernel that was installed originally by Ubuntu (2.6.24-24-server).</div><div>The problem still exists and I know for sure it didn't when things were first setup.</div>
<div>- There's just no way we could have migrated 400gig of data onto the RAID if it was this flakey.</div><div><br></div><div>Whatever it is is hardware related, and it seems to be getting worse over time...</div><div>
<br></div><div><br></div><div>David</div><div><br></div></div>