> > > I ended up with corrupted ext3 (see sparc.jpg) and working now to restore
> > > it.
> >
> > Up and running again. I managed to get some more info from yesterday crash
> > from syslog:
>
> I've seen similar corruptions with an Intel SSD drive on an MPT Fusion
> SAS interface, which also goes through scsi like your sym case here.
>
> But I'm pretty sure I also saw them with 2.6.28, were you able to run
> 2.6.28 cleanly?
The thing is the last time I run this sparc was somewhere in 2.6.27~2.6.28
window.
I didn't see anything like it at that time. I'll give a try to 2.6.28 but it
might
be hard to trigger it as I don't know what exactly caused it. Also yesterday
the very same kernel (f3b8436a) worked under I/O load for hours just fine.
I'll leave it with 2.6.28 on it busy for a few days and see what happens.
Mariusz
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
