bug-ddrescue
[Top][All Lists]
Advanced

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

Re: [Bug-ddrescue] Feature Suggestion: Automatic Cooldown mode


From: David Deutsch
Subject: Re: [Bug-ddrescue] Feature Suggestion: Automatic Cooldown mode
Date: Thu, 6 Feb 2014 18:26:19 +0100

Wow, yeah, so it seems like i'm totally daft. I got confused by seeing
the pointer in ddrescueview around the same area as it was before.

Still: The 'reset to 0' thing I mentioned is something you might want
to look into. I'll keep you posted on whether or not the speed
improves.

-David

On Thu, Feb 6, 2014 at 6:02 PM, David Deutsch <address@hidden> wrote:
> Hmm, not sure that worked the right way:
>
> GNU ddrescue 1.18-pre7
> rescued:     1764 GB,  errsize:   8111 MB,  errors:   87250
> Current status
> rescued:     1768 GB,  errsize:   8131 MB,  current rate:        0 B/s
>    ipos:   791401 MB,   errors:   93896,    average rate:    73307 B/s
>    opos:   791401 MB, run time:   16.09 h,  successful read:    4.06 m ago
> ^C
>
> $ sudo ddrescue -f -n -d -O -s 512 /dev/sdf /dev/sde logfile
>
> GNU ddrescue 1.18-pre7
> rescued:       512 B,  errsize:       0 B,  errors:       0
> Current status
> rescued:       512 B,  errsize:       0 B,  current rate:        0 B/s
>    ipos:         0 B,   errors:       0,    average rate:        0 B/s
>    opos:         0 B, run time:       0 s,  successful read:       0 s ago
> Finished
>
> $ sudo ddrescue -f -n -d -O -R /dev/sdf /dev/sde logfile
>
> GNU ddrescue 1.18-pre7
> rescued:     1768 GB,  errsize:   8131 MB,  errors:   93896
> Current status
> rescued:     1768 GB,  errsize:   8133 MB,  current rate:      256 B/s
>    ipos:     1934 GB,   errors:   93933,    average rate:      195 B/s
>    opos:     1934 GB, run time:   12.05 m,  successful read:       0 s ago
> Copying non-tried blocks...
>
> First up: Seeing EVERYTHING reset to 0 was /super/ scary. Really, really 
> scary.
>
> Second: ipos hasn't really changed. Did I do it wrong?
>
> -David
>
> On Thu, Feb 6, 2014 at 5:12 PM, Antonio Diaz Diaz <address@hidden> wrote:
>> David Deutsch wrote:
>>>
>>> As for reading it backwards: Can I even do that at this stage in the
>>> process?
>>
>>
>> Sure. First reset the current position with:
>>
>>   ddrescue your_options_and_files -s 512
>>
>> Then run in reverse:
>>
>>
>>   ddrescue your_options_and_files -R
>>
>>
>> Best regards,
>> Antonio.



reply via email to

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