Re: [Bug-ddrescue] interpreting ddrescue 1.21 terminal output

[Antonio Diaz Diaz]

Hello David,

David Kamaunu wrote:
> Now I have a question about the terminal output of concurrent project.  It
> seems that the program did two very large jumps.  The first from ipos 1147M
> to 1777M (630MB) and then again from 1777 to 2723 (946M).   Could you
> explain to me what the program is doing?

Ddrescue seems to be working right. It is the garbage characters shown 
in your images what is making the display jump a line up from time to 
time, making it appear as if the input position (ipos) had jumped forward.


> In addition I would like to ask if it is better to run a number of short
> runs or do relatively large chunks and let the application sip the drive
> for several days?

Unless the drive overheats or something, it is better to let ddrescue 
run until it finishes. (Which in your case may take 170 days for the 
whole drive at the current average rate).

I have noticed that you used two different mapfiles (recover and 
recover2). You must use the same mapfile in all runs for ddrescue to 
work correctly and not retry the same area more than once.

BTW, requesting retries and --no-scrape at the same time does not make 
much sense. I would just use --no-scrape.

Next time, please, send the screenshots as text, not as png images.

In case you need to send a mapfile to the list, remember to compress it 
first.


Best regards,
Antonio.