Dear Antonio,
I think there are certain scenarios which are not in the scope of what
ddrescue is expected to cover.
Of course you could implement to have it detect a lot of things that
might possibly happen beacuse the system ddrescue is run on is not
properly configured or because the administrator does something 'bad'
(e.g. mount the disk which ddrescue is trying to recover from, etc.).
But continuously checking for such possible hazards in the background
will just make the code more complex without any gain regarding the
primary goal of ddrescue - which from my understanding is to recover
data and not to "provide hints about best practices on system
administration while recovering data" ;-)
Kind Regards
Felix
On 10.11.2012 21:04, Antonio Diaz Diaz wrote:
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.
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
