bug-ddrescue
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ddrescue] direct mode with AF disks, exit on slow, save mapfile


From: Antonio Diaz Diaz
Subject: Re: [Bug-ddrescue] direct mode with AF disks, exit on slow, save mapfile interval, Russian translation
Date: Sat, 18 Jun 2016 14:13:45 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.8.1.4) Gecko/20070601 SeaMonkey/1.1.2

Hello Dmitry,

Dmitry Kostin wrote:
1) Please, add an option to quit or, better, to pause the program or
to reset/reinit/power_cycle the input hard drive when skipping slow
areas. If made to quit - I can use a shell script to pause and
restart the copying (in cycle).

Quitting is the most flexible option. As you say, it allows to script whatever action the drive may need.

Or maybe the syntax of --min-read-rate could be extended to:

  --min-read-rate=<bytes>,<pause>

where <pause> is the amount of seconds to pause after each slow read. A <pause> of 0 could make ddrescue quit.

Additionally, ddrescue could reopen the input file every time it pauses because of a slow read.

What do you think?


Also, when the program is used on a device with surface scratches or
with one slow head - I need the program to stop immediately when
speed falls, without any more tries to read damaged areas. So, if it
reads stably (from "stable") at 15 Mb/s and falls to 8 or less - STOP
immediately. Is it possible to do so?

Yes, with the extension to --min-read-rate explained above, for example.


2) The second my question is about using direct mode on disks with
advanced format. Both input and output devices have native sector
sizes of 4kb (emulated to OS as 512 bytes) and size of 3000Gb.

Maybe the OS emulation introduces an offset that prevents ddrescue to read the real sectors at the right positions?


3) Can you add (return/implement back) the option of
log_saving_time_interval or just make it static, about 30 seconds. As
I remember, it existed in earlier versions.

What versions? According to the ChangeLog, such option did never exist. Do you mean '--logfile size' ( which was removed in 1.19)?

In any case, I'll implement the option you ask in the next version.


Best regards,
Antonio.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]