Re: libata timeouts when stressing a Samsung HDD

[Tejun Heo <tj@kernel.org>]

Chuck Ebbert wrote:
> If I use an ext3 filesystem with noatime I never see problems, but if I use XFS
> with barriers and atime enabled, I keep getting this:
> 
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1.00: status: { DRDY }
> ata1: hard resetting link
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/133
> end_request: I/O error, dev sda, sector 13851948

ext3 doesn't use barrier by default.  Timing out on FLUSH_CACHE is a
pretty good sign that something is wrong with the disk.  Can you
please post the output of "smartctl -a /dev/sda"?

-- 
tejun