Re: getting I/O errors in super_written()...any ideas what would cause this?

[Chris Friesen <chris.friesen@genband.com>]

On 12/03/2012 03:21 PM, Dave Jiang wrote:
> On 12/03/2012 02:08 PM, Chris Friesen wrote:
>> On 12/03/2012 02:52 PM, Ric Wheeler wrote:
>>
>>> I jumped into this thread late - can you repost detail on the specific
>>> drive and HBA used here? In any case, it sounds like this is a better
>>> topic for the linux-scsi or linux-ide list where most of the low level
>>> storage people lurk :)
>> Okay, expanding the receiver list. :)
>>
>> To recap:
>>
>> I'm running 2.6.27 with LVM over software RAID 1 over a pair of SAS disks.
>> Disks are WD9001BKHG, controller is Intel C600.
>
> Just curious what driver are you using with the C600. The upstream
> driver for C600 didn't get accepted until 3.0-rc6 and all of the
> outstanding patches weren't accepted until 3.7-rc. So I'd say 3.6 would
> be your best bet until 3.7 is released. Did you attempt a backport of
> the isci driver or using something like an LSI port on 2.6.27? Have you
> verified the issue on a more recent kernel?

We're using a driver provided by the hardware vendor.  It appears to be 
a backport of version 1.0.1 of the isci driver.  We've been using it 
since mid-March or so.

This is an embedded system, so as is all too common in that environment 
upgrading the whole kernel isn't an option since it requires support 
from multiple hardware/software vendors.

Upgrading just the driver might be possible--do you think it's likely as 
a cause for these errors?  The current driver has a binary firmware file 
that it uses--would we keep that with the new driver?

Chris