Description of problem: Random device resets causing data loss. Version-Release number of selected component (if applicable): 3.2.9-1.fc16.x86_64.debug How reproducible: This problem appears to be randomly occurring and not especially associated with heavy I/O. One failure occurred with the device NOT mounted and NO I/O activity. Steps to Reproduce: 1.Connect the device and power it on 2.System sees the device 3.Mount the device 4.Use the drive and wait for this problem to happen. Actual results: See above. Expected results: Normal drive operations. Additional info:
Created attachment 569546 [details] redacted /var/log/messages This bug has a lot of similarities to this bug, "Bug 782280 - ext4 write took more than 2 minutes to complete"
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Dave, I just tested and after a few minutes got the same result. Do you need more information? Regards, George...
Created attachment 572377 [details] gzip'd copy of parts of /var/log/messages during a problem event. Dave, Here's the excerpt from /var/log/messages for the time when this latest problem appeared. I'm wondering if my setup is the problem. I have a usb-splitter 1 in, 4 out which connects one of the 4 to a KingWin usb/sata external connector. Regards, George...
Dave, This time I used the cp command to create the problem instead of a "tar -cvlf - * | (cd /sdc1/wtf;tar -xvpf -)" The key message looks like this: " 1210 [52205.619432] sd 10:0:0:0: [sdb] Unhandled error code"
Dave, I have been running on this kernel: "3.3.0-8.fc16.x86_64.debug #1 SMP Thu Mar 29 18:14:11 UTC 2012 x86_64 GNU/Linux" for the past 3 days + and have NOT seen this error. I would say that this bug is fixed now (knock on wood). Thanks for your help! George... 00:01am up 3 days 11:35, 16 users, load average: 1.18, 1.00, 0.97
Thank you for letting us know.
Created attachment 577012 [details] gzip'd copy of parts of /var/log/messages during a problem event. Josh, I spoke too soon. I'm enclosing an excerpt from /var/log/messages that shows this problem but there's also a stack dump and some other messages that I'm thinking you might find interesting. If I need to file a new bug for the stack dump, let me know and, if you can, please suggest who I should send it to. Regards, George...
Created attachment 581932 [details] Clip from /var/log/messages Josh, This just happened a few minutes ago after several days of blissfull operation. George...
Josh, This problem just re-appeared from my making a 1TB Seagate laptop drive busy. Effectively, the hardware has not changed except for the new drive. Sigh. I'm enclosing excerpts from /var/log/messages. There's a trace dump in this file. Perhaps this will lead to a solution of this problem? Regards, George...
Created attachment 619323 [details] gzip'd exerpts from /var/log/messages relating to this problem