Re: libata interface fatal error

[Tejun Heo <htejun@gmail.com>]

Florian Effenberger wrote:
>> Looks like a genuine transmission/interface error to me.  How often does
>> this occur?  Please try to connect the drive to another port using and
>> possibly different power lane.  Also, testing with another drive is a
>> good way to track down where the problem is.
> 
> it occurs as soon as the drive is being used heavily (load of about 2,x
> on the machine when running our test scripts). About 15 times in 2 or 3
> hours. Will try to change port, power supply and drive.
> 
>> Yeah, libata EH is working properly so there shouldn't be any problem
>> other than the error messages and a bit slower transfer speed.
> 
> So, even if the errors are still there, there is nothing real to worry
> about for me?

Data integrity wise there should be no problem but your error rate is
pretty high and eventually will make libata turn off NCQ and/or speed
down PHY speed.

> There are now new errors with hard errors, is this still ok?
> 
> ===
> ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> ata4.00: cmd 60/80:00:00:09:97/00:00:0a:00:00/40 tag 0 cdb 0x0 data
> 65536 in
>          res 40/00:04:00:67:14/00:00:1c:00:00/40 Emask 0x4 (timeout)

Yeap, your data is safe.  With timeouts, data transfer speed can be much
lower tho.  It definitely seems something is wrong with your hardware setup.

-- 
tejun