Hello ddrescue-Team, I dont want to report a bug, but I have a question about the behavior of ddrescue v1.7.
I tried to save a partition /dev/hda1 into a file /media/hdb1/imagefile. Logfile is also there /media/hdb1/logfile. This worked fine until the error in the 25 GByte Parition at nearly 9GByte. At the error of course the data transferrate broke down from about 8 MByte/s to 35 kByte/s. Thats ok. A long time I was waiting for the transferrate to increase again, because there are no more errors in the partition as far as I know. But after 4 hours and about 0,5 Gbyte the datarate didn't increase. So it would take about 4 days for the rest of the partition and I interrupted with Ctrl-C at first. Commandline was: ddrescue -n /dev/hda1 /media/hdb1/imagefile /media/hdb1/logfile My question is: is this behavior normal or could I call a commandline option so that ddrescue will adapt the datatrate to the errorrate. Or is there a way to stop reading after the error, then read from this position with the same image, new logfile and high datatrate and the image will be concatenated together: ddrescue -n -s errorpos+errorlenght /dev/hda1 /media/hdb1/imagefile /media/hdb1/logfile1 ddrescue -n -i errorpos+errorlenght+1 -o errorpos+errorlenght+1 /dev/hda1 /media/hdb1/imagefile /media/hdb1/logfile2 ? I hope you could understand what I mean, my english isn't too bad and my questions aren't too stupid. Thanks a lot. Wolfgang _______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
