Re: [Bug-ddrescue] Problem with domain-logfile

[Antonio Diaz Diaz]

Florian Sedivy wrote:
> Btw, I would wish for an option to exit a run _before_ the trimming
> phase (e.g. -N, --no-trim), because trimming already switches from
> cluster- to block-reading.

This can easily be done. But to give the user full control it should 
just skip the trimming phase instead of "exiting the run". The latter 
could then be achieved with "ddrescue --no-trim --no-split".


> But all this leads to more changes in code than just loose syntax
> checking, I guess?

Sure! Something like a "-L, --domain-list" option would be needed.


> One possibility would be to use the different status markers from the
> domain-logfile in their original meaning to override the "initial
> status read from log file" just once at the beginning of the run
> (first or last occurrence of the same block wins). This would allow
> to selectively retrim or re-copy certain areas without having to
> alter the original (regular) log file.

Retrimming or re-copying certain areas can already be done with a domain 
logfile:

`-A'
`--try-again'
     Mark all non-split and non-trimmed blocks inside the rescue domain
     as non-tried before beginning the rescue.

`-M'
`--retrim'
     Mark all failed blocks inside the rescue domain as non-trimmed
     before beginning the rescue.


> Finally, using only a domain-logfile with status-overrides _without_
> a regular log file, the domain-logfile would become the sole source
> for the "initial status" of a block. Strictly processing the
> domain-logfile line by line - together with the new enhanced
> logging-features of ddrescue - could come in handy for all sorts of
> test-cases.

This defeats ddrescue's strategy of trimming and splitting the largest 
blocks first, and could probaby be achieved with a regular logfile 
combined with the --domain-list option above.

I'll first release 1.18-pre5 with the logfile changes to ddrescue and 
ddrescuelog. Then I'll think about the other ideas. :-)


Best regards,
Antonio.