I would love to see it fixed in the kernel. But hell, I can't even
consistently reproduce it now. The test drive I was just working with
that was producing the problem has now stopped producing the problem. Go
figure. And I actually used a hammer to "simulate" a failing drive
problem on that drive (I don't have a large collection of failing
drives). Yes, I said a hammer, always thinking creatively :) But if
there is anything I can do to help report the problem, then please let
me know.
Scott
On 8/25/2013 6:55 PM, Antonio Diaz Diaz wrote:
Paul L Daniels wrote:
I can confirm that closing and reopening after a
detected slowdown still has a positive effect, and brings the read
speed back up. This makes it a little bit more tricky to implement
though...
Maybe we need an entirely different approach - namely we need to post
this as a potential bug in the linux kernel?
Sure. The difficult part is preparing a test case so that the kernel
developers can reproduce the problem. ;-)
Best regards,
Antonio.
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
