"Trapping" hard drive errors ( "ata***** failed command: READ FPDMA QUEUED")

[Mouse Dresden]

Hello I hope that this question is not to mundane.

A while ago I encountered this error message on a hard drive of mine.
I managed to clean up the problem and run smartctl and the disk is
clean, but such errors can be very problematic. I think one of the
reasons is that the hard drive gets "bogs down" on the particular
command and communication between the kernel and drive, other system
calls time out. This generates a lot of spurious errors you have to
eliminate.

I would like to create some basic tools to aid in diagnosing and
repairing such problems. The main difficulty is "trapping" the error
message. By this I mean terminating the call that is causing the
error, causing the drive to abandon this particular command, and
sending some sort of signal ( figurative and or literal ) to the
process making the particular command, so I can trace it.

Can someone either describe the process, or if it is too long,
recommend some reading describing it?

If it helps to know the detailed message, it can be found at:
http://unix.stackexchange.com/questions/43681/kde-causes-read-fpdma-queued-error

Thank you
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/