Created attachment 503722 [details]
Excerpt from dmesg when the error occurred

Description of problem:

My system recently "froze" after receiving the following error message in my dmesg logs:

[1805302.253343] sd 4:0:0:0: [sdb] Unhandled error code
[1805302.253347] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
[1805302.253352] sd 4:0:0:0: [sdb] CDB: Write(10): 2a 00 00 89 12 eb 00 00 10 00
[1805302.253365] end_request: I/O error, dev sdb, sector 8983275
[1805302.253389] Aborting journal on device sdb3.
[1805302.253623] __journal_remove_journal_head: freeing b_committed_data
[1805302.254189] EXT3-fs (sdb3): error: ext3_journal_start_sb: Detected aborted journal
[1805302.254195] EXT3-fs (sdb3): error: remounting filesystem read-only
...

The filesystem then got mounted read-only and I had to reboot (and manually fsck).

I suspect this might have been triggered by running a daily (automatically scheduled) SMART selftest, but I'm not sure.

I'm attaching excerpts from dmesg and /var/log/messages when it occurred, as well as other information about my machine.

Version-Release number of selected component (if applicable):

kernel-2.6.35.13-91.fc14.x86_64

How reproducible:

It has happened once before, but I don't know how to force it to occur.