Andrew, Thanks for the advice.
As you say, shifting to EXT4 solved the problem. The drive finished converting to an image file at 50MB/s (compared with about 200KB/s that it had dropped to!). The odd thing is that it had been averaging 30MB/s for the first 100GB without any sign of slow up on NTFS, but at an unknown point plummeted, suggesting there is a bug somewhere. Clearly it is a problem particularly with only large NTFS files. I wonder if this is a: * a general Linux NTFS problem; * an NTFS driver problem (that might be solved by using a different NTFS driver); * or unique to ddrescue and the way it works? Either way I'm sold that EXT3/EXT4 is best for running ddrescue for now. I'm also sold on using image files rather than cloning drives, it is just much more flexible. For reference, the bigger plan seems to have worked, and am now back to running data recovery from the failing drive but into the image-file instead using the original logfile. (Of course I could be capturing gibberish, but logic says it should be just fine!) Thanks again Mike -- View this message in context: http://old.nabble.com/Change-from-Disk-Cloning-to-File-Image-half-way-through--tp30366546p30366723.html Sent from the Gnu - ddrescue mailing list archive at Nabble.com. _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org http://lists.gnu.org/mailman/listinfo/bug-ddrescue
