Hello,
Pete Holzmann wrote:
-J seems to only work correctly if, in the *current run* there has been a
successful read.
True.
But once I power cycle the drive and restart ddrescue, it will run for minutes
or hours without ever stopping.
Shouldn't it, after seeing an error, go to ANY already-known-good-block and do a
test read to ensure the drive is still responsive?
It could, but this would have some drawbacks:
- It complicates the code because there is no such thing as an
"already-known-good-block"; any block succesfully read in a previous run
may be unreadable now.
- Data consistency can't be verified unless the data is also read from
outfile, which ddrescue currently opens read-only.
Does anybody think that this change is worth the trouble?
Best regards,
Antonio.
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
