Re: errors from mptsas

[Wakko Warner <wakko@animx.eu.org>]

Rick Warner wrote:
> I am working on 2 dual opteron systems using LSI 3041E SAS cards (1064E(b3)).  
> They each have (1) 73G Seagate SAS drive and (2) 750G Seagate SATA drives 
> hooked up to them.
> 
> One of the stress tests we run on systems is looping through the hard drives 
> running "dd if=/dev/sdX of=/dev/null". With that running, we get a steady 
> stream of these errors in the dmesg-
> 
> mptbase: ioc0: LogInfo(0x31123000): Originator={PL}, Code={Abort}, 
> SubCode(0x3000)
> 
> Any idea what's going on here? I have already updated to the latest firmware 
> for the card.  The system is loaded with FC8 running 2.6.24.4-64.fc8.

Join the club.  I have an LSI SAS with 3x 750gb seagate sata drives in
raid5.  Does this happen only on your SATA drives or all the drives?
Depending on the activity, it would drop one of them out of the
array.  I think the problem has been solved for now by changing the
queue_depth to 1.

echo 1 > /sys/block/sdX/device/queue_depth

Here's the drives in my system:
[0:0:0:0]    disk    ATA      ST3750640AS      E     /dev/sda
[0:0:1:0]    disk    ATA      ST3750640AS      E     /dev/sdb
[0:0:2:0]    disk    ATA      ST3750640AS      E     /dev/sdc

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???