On Mon, May 21, 2012 at 10:58:30AM +0100, Brian Candler wrote:
> On Mon, May 21, 2012 at 09:59:03AM +1000, Dave Chinner wrote:
> > You need to provide the output of sysrq-W at this point ('echo w >
> > /proc/sysrq-trigger') so we can see where these are hung. the entire
> > dmesg would also be useful....
>
> Thank you for this advice Dave.
>
> Attached is the full dmesg output after another hang. The sysrq output is
> near the end, at timestamp 250695.
It has recently been pointed out to me that the original attachment was
incomplete and didn't include the sysrq output. Attached is the dmesg file
*with* the sysrq data at the given timestamp.
Unfortunately, I have been trying to reproduce this problem on an identical
box and over 5 days the problem didn't reoccur. (Aside: that was until one
of the RAID0 drives failed, which is turning out to be a common occurrence
with Seagates; but that's not the failure I was seeing before, which I used
to be able to replicate in less than an hour. In this case XFS shut down
gracefully in the face of I/O errors)
This isn't one of the three actual boxes which had locked up before, but
it's another box with identical chassis and motherboard bought from same
supplier. This however has an up-to-date Ubuntu 12.04 kernel on it, so it's
possible there has been some driver fix since my original tests.
I will continue to investigate.
Regards,
Brian.
Attachment:
storage3-sysreq.txt.gz
Description: application/gunzip
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
