No, but now that you say that if the system is unable to write to the RAID5 which contains the log file would this even happen?<div><br></div><div>e.g. /var is the problematic RAID5 partition and when it locks up it takes out one or more of the physical disks.</div>
<div><br></div><div>An interesting observation is that when the problem occurs it either locks up both sda & sdb, or sdc by itself.</div><div>I am guessing that this is because sda & sdb are on the same channel, so either the channel itself is going or one of the disks is which is taking the other with it.</div>
<div><br></div><div><br>David</div><div><br></div><div><br><br><div class="gmail_quote">On Thu, Mar 25, 2010 at 12:14 AM, Daniel Reurich <span dir="ltr"><<a href="mailto:daniel@centurion.net.nz">daniel@centurion.net.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Does anything show up in the syslog or dmesg that indicates sata i/o<br>
port resets or anything like that??<br>
<font color="#888888"><br>
Daniel Reurich<br>
</font><div><div></div><div class="h5"><br>
On Wed, 2010-03-24 at 20:53 +1300, David Harrison wrote:<br>
> On Wed, Mar 24, 2010 at 6:36 PM, Daniel Pittman <<a href="mailto:daniel@rimspace.net">daniel@rimspace.net</a>><br>
> wrote:<br>
> David Harrison <<a href="mailto:david.harrison@stress-free.co.nz">david.harrison@stress-free.co.nz</a>> writes:<br>
><br>
><br>
> > I will try the deadline scheduler tonight and see if that<br>
> makes a<br>
> > difference.<br>
><br>
><br>
> You should be able to make the change at run-time, through<br>
> sysfs, I believe.<br>
> It is a property of the hardware devices, IIRC, in sysfs.<br>
><br>
><br>
><br>
><br>
> I tried out a few of the schedulers and none of them helped the<br>
> problem.<br>
> If anything I'd have to say it got worse.<br>
><br>
><br>
> As a final test I have switched to the kernel that was installed<br>
> originally by Ubuntu (2.6.24-24-server).<br>
> The problem still exists and I know for sure it didn't when things<br>
> were first setup.<br>
> - There's just no way we could have migrated 400gig of data onto the<br>
> RAID if it was this flakey.<br>
><br>
><br>
> Whatever it is is hardware related, and it seems to be getting worse<br>
> over time...<br>
><br>
><br>
><br>
><br>
> David<br>
><br>
><br>
</div></div><div class="im">> --<br>
> Wellington Linux Users Group Mailing List: <a href="mailto:wellylug@lists.wellylug.org.nz">wellylug@lists.wellylug.org.nz</a><br>
> To Leave: <a href="http://lists.wellylug.org.nz/mailman/listinfo/wellylug" target="_blank">http://lists.wellylug.org.nz/mailman/listinfo/wellylug</a><br>
<br>
<br>
</div>--<br>
<div class="im">Daniel Reurich.<br>
<br>
Centurion Computer Technology (2005) Ltd<br>
Mobile 021 797 722<br>
<br>
<br>
<br>
<br>
--<br>
</div><div><div></div><div class="h5">Wellington Linux Users Group Mailing List: <a href="mailto:wellylug@lists.wellylug.org.nz">wellylug@lists.wellylug.org.nz</a><br>
To Leave: <a href="http://lists.wellylug.org.nz/mailman/listinfo/wellylug" target="_blank">http://lists.wellylug.org.nz/mailman/listinfo/wellylug</a><br>
</div></div></blockquote></div><br></div>