Petr Slansky wrote:
I didn't touch time manually. But there is ntpd deamon running on PartedMagic,
"ntpd -g".
You was right, it is issue related to time. Could you improve ddrescue to
handle similar situation?
It is difficult for ddrescue to correctly handle this situation because
it depends on a stable clock to calculate rates, time since last
successful read, slow reads, etc. For example, the "average rate" is
measured through the whole duration of the rescue. If ddrescue has been
running for two hours and then you put back the clock by one hour, the
average rate will apparently double.
This said, I can make ddrescue detect a change back in time (but not a
change forward) and warn the user that the rates, etc, may be (grossly)
inaccurate for the rest of the run.
Best regards,
Antonio.
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
